dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2024-33862

HIGH · 7.5 CVSS v3.1 Published 2024-07-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer-management vulnerability in OPC Foundation OPCFoundation.NetStandard.Opc.Ua.Core versions prior to 1.05.374.54 allows remote attackers to exhaust memory resources by sending excessive messages from a remote source, potentially causing a denial of service condition.

MitigationUpgrade OPCFoundation.NetStandard.Opc.Ua.Core to version 1.05.374.54 or later. Additionally, implement rate limiting and connection throttling on OPC UA servers to mitigate the risk of memory exhaustion from rapid message flooding.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the OPCFoundation.NetStandard.Opc.Ua.Core library
    Search for the file Opc.Ua.Core.dll in your application directories, Global Assembly Cache (GAC), or NuGet package restore location. On Windows, check the GAC using 'gacutil /l' or inspect your application's bin folder and referenced NuGet packages.
    Affected if The library is present in your environment
  2. Determine the installed version
    Right-click the Opc.Ua.Core.dll file, select Properties, and view the File Version or Product Version. Alternatively, check your project's packages.config, .csproj file, or NuGet package manager for the installed version of OPCFoundation.NetStandard.Opc.Ua.Core.
    Affected if The version number is lower than 1.05.374.54
  3. Verify if the system is configured as an OPC UA server
    Inspect your application configuration (app.config or appsettings.json) for endpoints defined under the 'Opc.Ua.Servers' section or review your code for instances of 'UA Server' or 'ServerEngine' classes from the OPC UA library.
    Affected if The system is configured to run as an OPC UA server accepting remote client connections
  4. Confirm network exposure of OPC UA endpoints
    Review your firewall rules and server binding configurations to determine if OPC UA TCP ports (default 4840) are exposed to untrusted networks. Check your endpoint configuration files for 'TransportQuotas' and 'MaxMessageQueueSize' settings.
    Affected if OPC UA endpoints are reachable from remote/untrusted networks without adequate throttling configured

Your environment is affected if OPCFoundation.NetStandard.Opc.Ua.Core version is below 1.05.374.54 AND your system is running as an OPC UA server exposed to remote connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OPCFoundation.NetStandard.Opc.Ua.Core to version 1.05.374.54 or later. Additionally, implement rate limiting and connection throttling on OPC UA servers to mitigate the risk of memory exhaustion from rapid message flooding.

Recommended fix High confidence

OPCFoundation.NetStandard.Opc.Ua.Core version 1.05.374.54 or later

  1. 1. Identify all projects in your solution that reference OPCFoundation.NetStandard.Opc.Ua.Core
  2. 2. Open the project file (.csproj) or package management console
  3. 3. Update the package reference to version 1.05.374.54 or later using: dotnet add package OPCFoundation.NetStandard.Opc.Ua.Core --version 1.05.374.54
  4. 4. Rebuild the solution to ensure the new package is integrated correctly
  5. 5. Test the application to verify the OPC UA server/client functions properly after the update
  6. 6. Deploy the updated application to production environments
Caveat Review OPC Foundation release notes for version 1.05.374.54 to check for any API changes that may affect existing code

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33862 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-33862 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data