Skip to main content
VulnerabilityPublished Updated

CVE-2024-45526: UA-.NETStandard · Unthrottled Resource Allocation

Affects UA-.NETStandardSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubopcfoundation/UA-.NETStandardpkg:github/opcfoundation/UA-.NETStandardOther threatsAffected
  • <=1.5.374.78
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Monitor OPC UA server logs for repeated authentication failures or unusual request patterns that may indicate exploitation attempts.
  2. Implement network-level protections such as firewalls and intrusion detection/prevention systems (IDS/IPS) to limit access to OPC UA servers only to trusted sources.
  3. Employ rate limiting or connection throttling on OPC UA endpoints to reduce the impact of repeated invalid authentication requests.
  4. Segment industrial control networks to isolate OPC UA servers from general enterprise networks and the internet, minimizing exposure.
  5. Stay informed about updates from the OPC Foundation and apply security patches or library updates promptly once they are released.
  6. Conduct regular security assessments and penetration testing focused on industrial communication protocols to identify and remediate similar resource exhaustion vulnerabilities.
  7. Consider deploying anomaly detection solutions tailored for industrial protocols to detect early signs of denial-of-service attacks.

Description

An issue was discovered in OPC Foundation OPCFoundation/UA-.NETStandard through 1.5.374.78. A remote attacker can send requests with invalid credentials and cause the server performance to degrade gradually.

References

Community reviews

Loading reviews…