Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet

GHSA-4cvp-hr63-822j

MEDIUM

Exposure of Sensitive Information in OPC UA .NET Standard Reference Server

Also known asCVE-2023-31048
Published
May 5, 2023
Updated
Oct 9, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk52th percentile+0.43%
0.00%0.43%0.86%1.29%0.4%0.8%Dec 25Apr 26Jun 26

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

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

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 Reference Server that allows remote attackers to send malicious requests that expose sensitive information.

https://files.opcfoundation.org/SecurityBulletins/OPC%20Foundation%20Security%20Bulletin%20CVE-2023-31048.pdf

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetOPCFoundation.NetStandard.Opc.Ua.Coreall versions1.4.371.86
.NETNuGetOPCFoundation.NetStandard.Opc.Ua.Serverall versions1.4.371.86

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

  2. Fix

    Update OPCFoundation.NetStandard.Opc.Ua.Core to 1.4.371.86 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4cvp-hr63-822j 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 pinpoints whether GHSA-4cvp-hr63-822j 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-4cvp-hr63-822j. 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 Reference Server that allows remote attackers to send malicious requests that expose sensitive information. https://files.opcfoundation.org/SecurityBulletins/OPC%20Foundation%20Security%20Bulletin%20CVE-2023-31048.pdf
O3 Security · Impact-Aware SCA

Is GHSA-4cvp-hr63-822j in your dependencies?

O3 detects GHSA-4cvp-hr63-822j across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-4cvp-hr63-822j: OPCFoundation.NetStandard… Information Dis… | O3 Security