NuGet (.NET)

Microsoft.Owin Known Vulnerabilities & Fixes

Microsoft.Owin has 2 known security vulnerabilities in NuGet (.NET). Upgrade to version 4.2.2 or later to resolve all known issues. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.

2 Vulnerabilities

Low Immediate Risk

No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.

Recommended safe version: 4.2.2

Upgrading to 4.2.2 or later resolves all 2 known vulnerabilities in Microsoft.Owin. Run: dotnet add package Microsoft.Owin --version 4.2.2

Is Microsoft.Owin in your project?

Check if you're affected and upgrade to 4.2.2 to stay secure.

Start Free Scan Get Alerted When New CVEs Drop

Total

Critical

High

Medium

Low

Security Summary

2 affected version ranges have been identified across these 2 advisories.
100% of known issues have a published fixed version.
Remediation: dotnet add package Microsoft.Owin

Vulnerabilities

2 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details. First disclosed May 24, 2022, most recently Aug 30, 2022 (98 days apart).

CVE / GHSA	Severity	CVSS	EPSS	Summary	Affected	Fixed In
CVE-2022-29117 .NET Denial of Service Vulnerability	HIGH	7.5	—	.NET Denial of Service Vulnerability	1.1.0-beta1, 1.1.0-beta2, 2.0.0, 2.0.0-rc1 (+20 more)	4.2.2
CVE-2020-1045 Cookie parsing failure	HIGH	7.5	—	Cookie parsing failure	1.1.0-beta1, 1.1.0-beta2, 2.0.0, 2.0.0-rc1 (+17 more)	4.1.1

About This Data

Vulnerability data for Microsoft.Owin is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.

CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.