How severe is GHSA-fvxf-r9fw-49pc?

GHSA-fvxf-r9fw-49pc has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-fvxf-r9fw-49pc?

GHSA-fvxf-r9fw-49pc affects the following packages: OPCFoundation.NetStandard.Opc.Ua.Core (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-fvxf-r9fw-49pc?

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

How do I detect GHSA-fvxf-r9fw-49pc 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 GHSA-fvxf-r9fw-49pc 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 GHSA-fvxf-r9fw-49pc?

O3 pinpoints whether GHSA-fvxf-r9fw-49pc 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 GHSA-fvxf-r9fw-49pc actively exploited in the wild?

No public exploit code has been indexed for GHSA-fvxf-r9fw-49pc 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.

What is the EPSS score for GHSA-fvxf-r9fw-49pc?

GHSA-fvxf-r9fw-49pc has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 70th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fvxf-r9fw-49pc?

GHSA-fvxf-r9fw-49pc is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-fvxf-r9fw-49pc published, and has it been updated?

GHSA-fvxf-r9fw-49pc was published on June 17, 2022 and was last updated on February 16, 2024. 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

GHSA-fvxf-r9fw-49pc

HIGH

Incorrect Implementation of Authentication Algorithm in OPCFoundation.NetStandard.Opc.Ua.Core

Also known asCVE-2022-29865

Published

Jun 17, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk70th percentile+0.80%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

A vulnerability was discovered in the OPC UA .NET Standard Stack that

allows a malicious client or server to bypass the application authentication mechanism
and allow a connection to an untrusted peer.

Affected Packages

1 total 1 fixed

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

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.4.368.58 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fvxf-r9fw-49pc 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 GHSA-fvxf-r9fw-49pc 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 GHSA-fvxf-r9fw-49pc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability was discovered in the OPC UA .NET Standard Stack that - allows a malicious client or server to bypass the application authentication mechanism - and allow a connection to an untrusted peer.

O3 Security · Impact-Aware SCA

Is GHSA-fvxf-r9fw-49pc in your dependencies?

O3 detects GHSA-fvxf-r9fw-49pc 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