cve.bz

CVE-2015-1637 (FREAK) microsoft: Cryptographic Issues

no score yetEPSS 13%Fix available

Known as FREAK

microsoft: no CVSS score yet. EPSS 13% estimated probability of exploitation activity in the next 30 days.

On this page
Schannel (aka Secure Channel) in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 does not properly restrict TLS state transitions, which makes it easier for remote attackers to conduct cipher-downgrade attacks to EXPORT_RSA ciphers via crafted TLS traffic, related to the "FREAK" issue, a different vulnerability than CVE-2015-0204 and CVE-2015-1067.
EPSS
13% (unchanged from 13% a week ago; 13% 30 days ago) estimated probability of exploitation activity in the next 30 days; 96th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-310 Cryptographic Issues
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-2015-1637 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2015-1637?via=ask-ai-copy and https://cve.bz/cve/CVE-2015-1637?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-2015-1637 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 NVD's CPE matches.

ProductAffected
microsoft:windows_server_2008r2:sp1
microsoft:windows_server_2012r2

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020659
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020660
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020661
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020662
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020663
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020664
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020665
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020666
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020667
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020668
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020669
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020672
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020673
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020674
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020675
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020676
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020677
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020678
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020679
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020680
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020681
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020682
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020630
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020631
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020632
  • Emerging Threats Open ET EXPLOIT FREAK Weak Export Suite From Server (CVE-2015-0204) sid 2020633
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020634
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020635
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020636
  • Emerging Threats Open ET POLICY FREAK Weak Export Suite From Client (CVE-2015-0204) sid 2020637

References

Check your stackJSON