dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2024-45526

MEDIUM · 5.3 CVSS v3.1 Published 2024-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
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.

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 · moderate confidence

In OPC UA .NETStandard servers through version 1.5.374.78, the authentication failure handling path does not properly release resources when processing requests with invalid credentials. A remote attacker can repeatedly send invalid authentication requests, causing gradual resource exhaustion and server performance degradation—a denial-of-service condition.

MitigationUpgrade OPCFoundation/UA-.NETStandard to a patched version beyond 1.5.374.78. As a compensating control, implement request rate limiting or connection throttling at the network perimeter to limit authentication failure attempts.

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
Low

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

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. Identify OPC UA .NETStandard version
    Locate the OPCFoundation/UA-.NETStandard assembly (UaCore.dll or similar) in your application or server installation directory. Right-click the DLL, select Properties, and inspect the File Version or Product Version field. Alternatively, check your project packages.config, .csproj file, or dependency management system for the installed NuGet package version.
    Affected if The version is 1.5.374.78 or earlier (including any 1.5.3xx.xx version below 1.5.374.79).
  2. Confirm OPC UA server is network-exposed
    Check your server configuration files (often named appsettings.json,UaServer.Config.xml, or similar) for the ServerInterface or Endpoint configuration section. Identify if any Endpoint URLs use net.tcp:// or opc.tcp:// protocols with IP addresses accessible from network segments outside your trust boundary.
    Affected if The server binds to a network-advertised IP address or hostname rather than localhost only, meaning external clients can reach the OPC UA endpoints.
  3. Verify authentication mechanisms enabled
    Inspect the server configuration for the SecurityPolicy and UserTokenPolicy settings under each Endpoint description. Look for settings that enable Username/UserPassword authentication or Certificate authentication, as these are the credential-based paths that trigger the flawed authentication failure handler.
    Affected if UsernamePassword or Certificate-based UserTokenPolicy is enabled on any exposed endpoint.
  4. Monitor for abnormal resource consumption
    If the server is already running, use system monitoring tools (Task Manager, Performance Monitor, or equivalent) to observe memory usage and open handle counts for the OPC UA server process over time, particularly after a period of failed login attempts.
    Affected if Memory or handles grow progressively without stabilization after repeated authentication failures.

You are affected if your OPC UA .NETStandard server runs version 1.5.374.78 or earlier, exposes network-accessible endpoints, and has credential-based authentication enabled.

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/UA-.NETStandard to a patched version beyond 1.5.374.78. As a compensating control, implement request rate limiting or connection throttling at the network perimeter to limit authentication failure attempts.

Recommended fix Moderate confidence

Upgrade to UA-.NETStandard version 1.5.374.79 or later (the first version after 1.5.374.78)

  1. 1. Identify the current version of OPC Foundation UA-.NETStandard in use by checking project references or NuGet packages.
  2. 2. Navigate to the official OPC Foundation GitHub repository or files.opfoundation.org to locate the latest stable release.
  3. 3. Upgrade the UA-.NETStandard library to a version newer than 1.5.374.78 (e.g., 1.5.374.79 or later if available).
  4. 4. Rebuild and test the application to ensure compatibility with the new library version.
  5. 5. Monitor server performance after deployment to verify the resource exhaustion issue is resolved.
Caveat Minor or patch updates typically have no breaking changes, but review release notes for any behavioral changes

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45526 — 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-45526 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