What is the CVSS score of CVE-2015-0005?

CVE-2015-0005 has a CVSS 2.0 base score of 4.3 (Medium). CVSS vector: AV:A/AC:M/Au:N/C:P/I:P/A:N. EPSS exploitation probability: 2.4%.

Is there a public PoC exploit available for CVE-2015-0005?

Yes, a public proof-of-concept exploit is available for CVE-2015-0005. Prioritise patching immediately. EPSS: 2.4%.

Windows Server 2008 CVE-2015-0005

MEDIUM

7PK - Security Features (CWE-254)

2015-03-11 secure@microsoft.com

Information Disclosure Microsoft Windows Server 2008 Windows Server 2012 Windows 2003 Server

4.3

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.3 MEDIUM

AV:A/AC:M/Au:N/C:P/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Adjacent

Attack Complexity

Confidentiality

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Mar 11, 2015 - 10:59 cve.org

MEDIUM 4.3

DescriptionCVE.org

The NETLOGON service in Microsoft Windows Server 2003 SP2, Windows Server 2008 SP2 and R2 SP1, and Windows Server 2012 Gold and R2, when a Domain Controller is configured, allows remote attackers to spoof the computer name of a secure channel's endpoint, and obtain sensitive session information, by running a crafted application and leveraging the ability to sniff network traffic, aka "NETLOGON Spoofing Vulnerability."

AnalysisAI

Technical ContextAI

This vulnerability is classified under CWE-254. The NETLOGON service in Microsoft Windows Server 2003 SP2, Windows Server 2008 SP2 and R2 SP1, and Windows Server 2012 Gold and R2, when a Domain Controller is configured, allows remote attackers to spoof the computer name of a secure channel's endpoint, and obtain sensitive session information, by running a crafted application and leveraging the ability to sniff network traffic, aka "NETLOGON Spoofing Vulnerability." Affected products include: Microsoft Windows 2003 Server, Microsoft Windows Server 2008, Microsoft Windows Server 2012.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.