CVE-2022-34716 — System.Security.Cryptogra…
MEDIUMCVE-2022-34716 is a medium-severity (CVSS 5.9) CWE-290 vulnerability in System.Security.Cryptography.Xml. A fix is available for System.Security.Cryptography.Xml — see the affected versions and patch details below.
.NET Information Disclosure Vulnerability
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-2022-34716.
EPSS Exploitation Probability
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.
How urgent is this, really
CVE-2022-34716 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
System.Security.Cryptography.Xml.NETSystem.Security.Cryptography.Xml.NETMicrosoft.AspNetCore.App.Runtime.win-x64.NETMicrosoft.AspNetCore.App.Runtime.win-x64.NETMicrosoft.AspNetCore.App.Runtime.linux-x64.NETMicrosoft.AspNetCore.App.Runtime.linux-x64.NETMicrosoft.AspNetCore.App.Runtime.win-x86.NETMicrosoft.AspNetCore.App.Runtime.win-x86+17 moreReal-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
.NET Spoofing Vulnerability
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | System.Security.Cryptography.Xml | all versions | 4.7.1dotnet add package System.Security.Cryptography.Xml --version 4.7.1 |
| .NETNuGet | System.Security.Cryptography.Xml | ≥ 5.0.0&&< 6.0.1 | 6.0.1dotnet add package System.Security.Cryptography.Xml --version 6.0.1 |
| .NETNuGet | Microsoft.AspNetCore.App.Runtime.win-x64 | ≥ 3.1.0&&< 3.1.28 | 3.1.28dotnet add package Microsoft.AspNetCore.App.Runtime.win-x64 --version 3.1.28 |
| .NETNuGet | Microsoft.AspNetCore.App.Runtime.win-x64 | ≥ 6.0.0&&< 6.0.8 | 6.0.8dotnet add package Microsoft.AspNetCore.App.Runtime.win-x64 --version 6.0.8 |
| .NETNuGet | Microsoft.AspNetCore.App.Runtime.linux-x64 | ≥ 3.1.0&&< 3.1.28 | 3.1.28dotnet add package Microsoft.AspNetCore.App.Runtime.linux-x64 --version 3.1.28 |
| .NETNuGet | Microsoft.AspNetCore.App.Runtime.linux-x64 | ≥ 6.0.0&&< 6.0.8 | 6.0.8dotnet add package Microsoft.AspNetCore.App.Runtime.linux-x64 --version 6.0.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for System.Security.Cryptography.Xml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update System.Security.Cryptography.Xml to 4.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-34716 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-34716 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-34716. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| .NET Core on Red Hat Enterprise Linux | rh-dotnet31-dotnet-0:3.1.422-1.el7_9 | RHSA-2022:6037 |
| .NET Core on Red Hat Enterprise Linux | rh-dotnet60-dotnet-0:6.0.108-1.el7_9 | RHSA-2022:6038 |
| Red Hat Enterprise Linux 8 | dotnet3.1-0:3.1.422-1.el8_6 | RHSA-2022:6057 |
| Red Hat Enterprise Linux 8 | dotnet6.0-0:6.0.108-1.el8_6 | RHSA-2022:6058 |
| Red Hat Enterprise Linux 9 | dotnet6.0-0:6.0.108-1.el9_0 | RHSA-2022:6043 |
Frequently Asked Questions
Is CVE-2022-34716 in your dependencies?
O3 Security finds CVE-2022-34716 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.