CVE-2024-33862: opcfoundation.netstandard.opc.ua.core · A Buffer-management
Affects opcfoundation.netstandard.opc.ua.coreSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 1.05.374.54 soon.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.05.374.54
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Upgrade opcfoundation.netstandard.opc.ua.core to 1.05.374.54.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
NuGetopcfoundation.netstandard.opc.ua.corepkg:nuget/opcfoundation.netstandard.opc.ua.coreOther threats | Affected
| 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. 2. Implement network-level rate limiting and filtering on OPC UA communication ports to restrict the volume of incoming messages from untrusted or external sources, mitigating memory exhaustion attempts. 3. Deploy intrusion detection and prevention systems (IDS/IPS) tuned to detect anomalous OPC UA traffic patterns indicative of flooding or DoS attacks. 4. Segment industrial networks to isolate OPC UA servers from general IT networks and the internet, reducing exposure to remote attackers. 5. Conduct regular security assessments and penetration testing of OPC UA implementations to identify and remediate potential weaknesses. 6. Maintain comprehensive logging and monitoring of OPC UA service health and resource utilization to enable rapid detection of abnormal memory consumption. 7. Educate operational technology (OT) and security teams about this vulnerability and establish incident response plans specific to OPC UA service disruptions. These steps go beyond generic advice by focusing on proactive network controls, segmentation, and operational monitoring tailored to the industrial context of OPC UA deployments.
Description
A buffer-management vulnerability in OPC Foundation OPCFoundation.NetStandard.Opc.Ua.Core before 1.05.374.54 could allow remote attackers to exhaust memory resources. It is triggered when the system receives an excessive number of messages from a remote source. This could potentially lead to a denial of service (DoS) condition, disrupting the normal operation of the system.