Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
HIGH severity

GHSA-qm9f-c3v9-wphv OPCFoundation.NetStandard…

HIGH

GHSA-qm9f-c3v9-wphv is a high-severity (CVSS 7.5) vulnerability in OPCFoundation.NetStandard.Opc.Ua.Core. A fix is available for OPCFoundation.NetStandard.Opc.Ua.Core — see the affected versions and patch details below.

Security Update for the OPC UA .NET Standard Stack

Published
Oct 18, 2024
Updated
Nov 28, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 28, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
.NETOPCFoundation.NetStandard.Opc.Ua.Core.NETOPCFoundation.NetStandard.Opc.Ua

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

This security update resolves a vulnerability in the OPC UA .NET Standard Stack that enables an unauthorized attacker to trigger a rapid increase in memory consumption.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetOPCFoundation.NetStandard.Opc.Ua.Coreall versions1.05.374.54dotnet add package OPCFoundation.NetStandard.Opc.Ua.Core --version 1.05.374.54
.NETNuGetOPCFoundation.NetStandard.Opc.Uaall versions1.05.374.54dotnet add package OPCFoundation.NetStandard.Opc.Ua --version 1.05.374.54

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for OPCFoundation.NetStandard.Opc.Ua.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update OPCFoundation.NetStandard.Opc.Ua.Core to 1.05.374.54 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qm9f-c3v9-wphv is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qm9f-c3v9-wphv can be triaged on real exposure rather than presence alone.

Tailored to GHSA-qm9f-c3v9-wphv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This security update resolves a vulnerability in the OPC UA .NET Standard Stack that enables an unauthorized attacker to trigger a rapid increase in memory consumption.
O3 Security · Impact-Aware SCA

Is GHSA-qm9f-c3v9-wphv in your dependencies?

O3 Security finds GHSA-qm9f-c3v9-wphv across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-qm9f-c3v9-wphv: High 7.5 severity | O3 Security