Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2025-2230

7.7 · HIGH

A flaw exists in the Windows login flow where an AuthContext token can be exploited for replay attacks and authentication bypass.

Published Mar 13, 2025CWE-287EPSS 0.24%

Overview

CVE-2025-2230 is a high-severity vulnerability. It was published on March 13, 2025 and has a CVSS 3.1 base score of 7.7 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.7, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

A flaw exists in the Windows login flow where an AuthContext token can

be exploited for replay attacks and authentication bypass.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

CISAwww.cisa.gov/news-events/ics-medical-advisories/icsma-25-072-01Refwww.philips.com/a-w/security/security-advisories.html

How CyberStrike helps

Frequently asked questions

What is CVE-2025-2230?

CVE-2025-2230 is a high-severity vulnerability. It was published on March 13, 2025 and has a CVSS 3.1 base score of 7.7 (HIGH).

How severe is CVE-2025-2230?

This vulnerability has a CVSS 3.1 base score of 7.7, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2025-2230?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-2230?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-2230 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999