CVE-2024-42513 — OPCFoundation.NetStandard…
MEDIUMCVE-2024-42513 is a medium-severity (CVSS 5.3) CWE-305 vulnerability in OPCFoundation.NetStandard.Opc.Ua.Bindings.Https. A fix is available for OPCFoundation.NetStandard.Opc.Ua.Bindings.Https — see the affected versions and patch details below.
Security Update for the OPC UA .NET Standard Stack
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-42513.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
OPCFoundation.NetStandard.Opc.Ua.Bindings.HttpsReal-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 allows an unauthorized attacker to bypass application authentication when using HTTPS endpoints.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | OPCFoundation.NetStandard.Opc.Ua.Bindings.Https | all versions | 1.5.374.158dotnet add package OPCFoundation.NetStandard.Opc.Ua.Bindings.Https --version 1.5.374.158 |
Affected Products
ua .net standard stackopcfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for OPCFoundation.NetStandard.Opc.Ua.Bindings.Https, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update OPCFoundation.NetStandard.Opc.Ua.Bindings.Https to 1.5.374.158 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-42513 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.
Frequently Asked Questions
Is CVE-2024-42513 in your dependencies?
Find it across NuGet, including transitive dependencies.