How severe is CVE-2024-42512?

CVE-2024-42512 has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-42512?

CVE-2024-42512 affects the following packages: OPCFoundation.NetStandard.Opc.Ua.Core (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2024-42512?

Update OPCFoundation.NetStandard.Opc.Ua.Core to 1.5.374.158 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-42512 is resolved across your whole dependency graph.

How do I detect CVE-2024-42512 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for OPCFoundation.NetStandard.Opc.Ua.Core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2024-42512 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2024-42512?

O3 pinpoints whether CVE-2024-42512 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2024-42512 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-42512 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2024-42512 published, and has it been updated?

CVE-2024-42512 was published on February 10, 2025 and was last updated on July 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

CVE-2024-42512

HIGH

CVE-2024-42512 is a high-severity (CVSS 8.6) vulnerability in OPCFoundation.NetStandard.Opc.Ua.Core. O3 Security confirms whether CVE-2024-42512 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Security Update for the OPC UA .NET Standard Stack

Also known asGHSA-h958-fxgg-g7w3

Published

Feb 10, 2025

Updated

Jul 15, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

.NETOPCFoundation.NetStandard.Opc.Ua.Core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`OPCFoundation.NetStandard.Opc.Ua.Core`	all versions	1.5.374.158

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for OPCFoundation.NetStandard.Opc.Ua.Core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update OPCFoundation.NetStandard.Opc.Ua.Core to 1.5.374.158 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-42512 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-42512 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-42512. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2024-42512 in your dependencies?

O3 detects CVE-2024-42512 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works