dbcve.org
Ua .net Standard StackApplication · Opcfoundation

CVE-2024-42512

HIGH · 8.6 CVSS v3.1 Published 2025-02-10
Fix available
A fix is available. Upgrade to 1.5.374.158 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Vulnerability in the OPC UA .NET Standard Stack before 1.5.374.158 allows an unauthorized attacker to bypass application authentication when the deprecated Basic128Rsa15 security policy is enabled.

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

The OPC UA .NET Standard Stack before version 1.5.374.158 contains an authentication bypass vulnerability in its handling of the deprecated Basic128Rsa15 security policy. An unauthenticated attacker can bypass application authentication when this legacy security policy is enabled, potentially gaining unauthorized access to OPC UA servers or clients.

MitigationUpgrade the OPC UA .NET Standard Stack to version 1.5.374.158 or later, and disable or remove the deprecated Basic128Rsa15 security policy from configurations.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ua .net Standard StackApplication
Affected:< 1.5.374.158

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
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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. Determine the installed version of the OPC UA .NET Standard Stack
    Check the version of the Opc.Ua.Core.dll assembly in the application bin folder, or inspect the NuGet package reference in the project file (packages.config or .csproj), or query the assembly version programmatically via the loaded DLL properties
    Affected if The version is lower than 1.5.374.158
  2. Locate OPC UA endpoint configuration files
    Search for configuration files that define OPC UA endpoints, typically named app.config, appsettings.json, or custom XML configuration files in the application directory or config folder
    Affected if Configuration files exist that define OPC UA server or client endpoint security settings
  3. Inspect the security policy configuration
    Open the configuration file and locate the SecurityPolicyUri or SecurityPolicy setting for each defined endpoint. Look for values indicating Basic128Rsa15 such as 'http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15' or 'Basic128Rsa15'
    Affected if Any endpoint configuration specifies Basic128Rsa15 as the security policy, especially if it is set as the minimum or default security policy
  4. Verify if Basic128Rsa15 is enabled in the server allowlist
    For OPC UA servers, check if Basic128Rsa15 appears in any AllowedSecurityPolicies, EnabledSecurityPolicies, or SecurityPolicies configuration section that defines which policies the server accepts from clients
    Affected if Basic128Rsa15 is listed in the server's allowed/enabled security policy list, indicating the deprecated policy is active

The environment is affected if the OPC UA .NET Standard Stack version is below 1.5.374.158 AND Basic128Rsa15 security policy is explicitly enabled or allowed in any endpoint configuration.

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
Upgrade available Upgrade to 1.5.374.158 or later
Fixed in 1.5.374.158
Interim mitigation

Upgrade the OPC UA .NET Standard Stack to version 1.5.374.158 or later, and disable or remove the deprecated Basic128Rsa15 security policy from configurations.

Recommended fix High confidence

1.5.374.158 or later

  1. 1. Identify all instances of OPC UA .NET Standard Stack in your environment that are running version < 1.5.374.158
  2. 2. Upgrade the OPC UA .NET Standard Stack to version 1.5.374.158 or later
  3. 3. After upgrading, verify that the Basic128Rsa15 security policy is either disabled or that the application authentication is now properly enforced
  4. 4. Test the OPC UA client and server communications to confirm secure operation
  5. 5. As an additional precaution, consider disabling the deprecated Basic128Rsa15 security policy entirely if not required for legacy compatibility
Caveat Minimal expected impact; however, verify that any legacy clients relying on Basic128Rsa15 are compatible with newer security policies

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

Fix this in Ua .net Standard Stack Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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