Home/CVE/The Credential Security Support Provider protocol (CredSSP) in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 S
CVE
CVE-2018-0886
The Credential Security Support Provider protocol (CredSSP) in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 S
The Credential Security Support Provider protocol (CredSSP) in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1 and RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, 1703, and 1709 Windows Server 2016 and Windows Server, version 1709 allows a remote code execution vulnerability due to how CredSSP validates request during the authentication process, aka "CredSSP Remote Code Execution Vulnerability".
HIGH · CVSS 7
EPSS 0.90997
Act now
- EPSS ≥ 0.50 - high probability of exploitation in the next 30 days
- EPSS percentile: top 0% of all CVEs by exploitation likelihood
- Public exploit or PoC is available
- CVSS base score ≥ 7.0
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2018-0886, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
8Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
T1040 · Network Sniffing T1134 · Access Token Manipulation T1185 · Browser Session Hijacking T1505.003 · Web Shell T1548 · Abuse Elevation Control Mechanism T1550.001 · Application Access Token T1557 · Adversary-in-the-Middle T1563 · Remote Service Session Hijacking
▤ Build a SIEM detection for these techniques
▤
CAPEC attack patterns
10Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-114 · Authentication Abuse CAPEC-CAPEC-115 · Authentication Bypass CAPEC-CAPEC-151 · Identity Spoofing CAPEC-CAPEC-194 · Fake the Source of Data CAPEC-CAPEC-22 · Exploiting Trust in Client CAPEC-CAPEC-57 · Utilizing REST's Trust in the System Resource to Obtain Sensitive Data CAPEC-CAPEC-593 · Session Hijacking CAPEC-CAPEC-633 · Token Impersonation CAPEC-CAPEC-650 · Upload a Web Shell to a Web Server CAPEC-CAPEC-94 · Adversary in the Middle (AiTM)
⬡
Weakness Classification
CWE-287Improper Authentication
▤
Affected Products & Versions
7microsoft windows 10all versions
microsoft windows 7all versions
microsoft windows 8.1all versions
microsoft windows rt 8.1all versions
microsoft windows server 2008all versions
microsoft windows server 2012all versions
microsoft windows server 2016all versions
⚠
Public Exploits & PoCs
19These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted.
📦
Fixed versions by distribution
6The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
suse sle15freerdp fixed in 0:2.0.0~rc4-3.3.1
suse sle15freerdp-devel fixed in 0:2.1.2-15.10.1
suse sle15freerdp-proxy fixed in 0:2.1.2-15.10.1
suse sle15libfreerdp2 fixed in 0:2.1.2-15.10.1
suse sle15libwinpr2 fixed in 0:2.0.0~rc4-13.2
suse sle15winpr2-devel fixed in 0:2.0.0~rc4-13.2
▣
Scoring & Timeline
7
HIGH · CVSS v3.0 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
⚑
Vendor Advisories
9suse-csafopenSUSE-SU-2025:15103-1
suse-csafopenSUSE-SU-2024:10768-1
suse-csafopenSUSE-SU-2024:12385-1
suse-csafSUSE-SU-2020:2272-1
suse-csafopenSUSE-SU-2019:0325-1
🔗
References & Sources
4Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0886PatchVendor Advisory