cve.bz

CVE-2020-1596 (Raccoon Attack) microsoft

5.4 mediumEPSS 0.9%Fix available

Known as Raccoon Attack

Medium (5.4) in microsoft. EPSS 0.9% estimated probability of exploitation activity in the next 30 days.

On this page
<p>A information disclosure vulnerability exists when TLS components use weak hash algorithms. An attacker who successfully exploited this vulnerability could obtain information to further compromise a users's encrypted transmission channel.</p> <p>To exploit the vulnerability, an attacker would have to conduct a man-in-the-middle attack.</p> <p>The update addresses the vulnerability by correcting how TLS components use hash algorithms.</p>

Severity

CVSS 3.1

5.4 medium
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 60th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-327 Use of a Broken or Risky Cryptographic Algorithm
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-1596 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-1596?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-1596?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-1596 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1803from 10.0.0 before publication
Microsoft Windows 10 Version 1809from 10.0.0 before publication
Microsoft Windows Server 2019from 10.0.0 before publication
Microsoft Windows Server 2019 (Server Core installation)from 10.0.0 before publication
Microsoft Windows 10 Version 1909from 10.0.0 before publication
Microsoft Windows Server, version 1909 (Server Core installation)from 10.0.0 before publication
Microsoft Windows 10 Version 1709 for 32-bit Systemsfrom 10.0.0 before publication
Microsoft Windows 10 Version 1709from 10.0.0 before publication
Microsoft Windows 10 Version 1903 for 32-bit Systemsfrom 10.0.0 before publication
Microsoft Windows 10 Version 1903 for x64-based Systemsfrom 10.0.0 before publication
Microsoft Windows 10 Version 1903 for ARM64-based Systemsfrom 10.0.0 before publication
Microsoft Windows Server, version 1903 (Server Core installation)from 10.0.0 before publication
Microsoft Windows 10 Version 2004from 10.0.0 before publication
Microsoft Windows Server version 2004from 10.0.0 before publication
Microsoft Windows 10 Version 1507from 10.0.0 before publication
Microsoft Windows 10 Version 1607from 10.0.0 before publication
Microsoft Windows Server 2016from 10.0.0 before publication
Microsoft Windows Server 2016 (Server Core installation)from 10.0.0 before publication
Microsoft Windows 7from 6.1.0 before publication
Microsoft Windows 7 Service Pack 1from 6.1.0 before publication
Microsoft Windows 8.1from 6.3.0 before publication
Microsoft Windows Server 2008 Service Pack 2from 6.0.0 before publication
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)from 6.0.0 before publication
Microsoft Windows Server 2008 Service Pack 2from 6.0.0 before publication
Microsoft Windows Server 2008 R2 Service Pack 1from 6.1.0 before publication
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)from 6.0.0 before publication
Microsoft Windows Server 2012from 6.2.0 before publication
Microsoft Windows Server 2012 (Server Core installation)from 6.2.0 before publication
Microsoft Windows Server 2012 R2from 6.3.0 before publication
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.0 before publication

Attack patterns (CAPEC)

  • CAPEC-20 Encryption Brute Forcing Likelihood: Low · Severity: Low
  • CAPEC-97 Cryptanalysis Likelihood: Low · Severity: Very High
  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-473 Signature Spoof
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-608 Cryptanalysis of Cellular Encryption Severity: High
  • CAPEC-614 Rooting SIM Cards Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON