CVE-2015-1635

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-02-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Exploited in the wild
9.8EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: >99.9%CVSS: 9.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

HTTP.sys in Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8, Windows 8.1, and Windows Server 2012 Gold and R2 allows remote attackers to execute arbitrary code via crafted HTTP requests, aka "HTTP.sys Remote Code Execution Vulnerability."

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that sooner than your standard update timelines at low mission impact and as soon as possible at medium or high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
>99.9%
EPSS %ILE
99th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that sooner than your standard update timelines at low mission impact and as soon as possible at medium or high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 14, 2015

Last Modified

April 22, 2026

Advisory Details (6)

Auto-updated Oct 8, 2026
Fix referenced — no release confirmed yet.
generic

CVE-2015-1635 - PSIRT.COM

http://www.securityfocus.com/bid/74013
generic

Packet Storm

http://packetstormsecurity.com/files/131463/Microsoft-Windows-HTTP.sys-Proof-Of-Concept.html
generic

Microsoft Windows - 'HTTP.sys' HTTP Request Parsing Denial of Service (MS15-034) - Windows dos Exploit

https://www.exploit-db.com/exploits/36776/
generic

Microsoft Windows - 'HTTP.sys' (PoC) (MS15-034) - Windows dos Exploit

https://www.exploit-db.com/exploits/36773/
generic

Microsoft Security Bulletin MS15-034 - Critical | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-034
generic
http://www.securitytracker.com/id/1032109

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 46× in last 7d / 202× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 908 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 808 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 13:40 UTCEG score recompute
  2. 2026-10-11 13:39 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  3. 2026-10-11 13:36 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  4. 2026-10-11 09:44 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  5. 2026-10-11 05:54 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  6. 2026-10-11 02:04 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  7. 2026-10-10 22:12 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  8. 2026-10-10 18:22 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  9. 2026-10-10 14:32 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  10. 2026-10-10 10:42 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  11. 2026-10-10 06:51 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  12. 2026-10-10 03:02 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  13. 2026-10-09 23:12 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  14. 2026-10-09 19:21 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  15. 2026-10-09 15:31 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  16. 2026-10-09 11:41 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  17. 2026-10-09 07:50 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  18. 2026-10-09 04:00 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  19. 2026-10-09 00:09 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  20. 2026-10-08 20:19 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  21. 2026-10-08 16:28 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  22. 2026-10-08 12:33 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  23. 2026-10-08 08:43 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  24. 2026-10-08 04:53 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  25. 2026-10-08 01:03 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
Show 75 more
  1. 2026-10-07 21:12 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  2. 2026-10-07 17:21 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  3. 2026-10-07 13:29 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  4. 2026-10-07 09:39 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  5. 2026-10-07 05:50 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  6. 2026-10-07 02:00 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  7. 2026-10-06 22:10 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  8. 2026-10-06 18:20 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  9. 2026-10-06 14:31 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  10. 2026-10-06 10:41 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  11. 2026-10-06 06:51 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  12. 2026-10-06 03:00 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  13. 2026-10-05 23:10 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  14. 2026-10-05 19:16 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  15. 2026-10-05 15:24 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  16. 2026-10-05 11:33 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  17. 2026-10-05 07:44 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  18. 2026-10-05 03:54 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  19. 2026-10-05 00:03 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  20. 2026-10-04 20:13 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  21. 2026-10-04 16:21 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  22. 2026-10-04 12:31 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  23. 2026-10-04 08:41 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  24. 2026-10-04 04:51 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  25. 2026-10-04 01:01 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  26. 2026-10-03 21:10 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  27. 2026-10-03 17:20 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  28. 2026-10-03 13:31 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  29. 2026-10-03 09:40 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  30. 2026-10-03 05:49 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  31. 2026-10-03 01:58 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  32. 2026-10-02 22:08 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  33. 2026-10-02 18:18 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  34. 2026-10-02 14:28 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  35. 2026-10-02 10:34 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  36. 2026-10-02 06:41 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  37. 2026-10-02 02:50 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  38. 2026-10-01 22:57 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  39. 2026-10-01 19:07 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  40. 2026-10-01 15:17 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  41. 2026-10-01 11:27 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  42. 2026-10-01 07:38 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  43. 2026-10-01 03:48 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  44. 2026-09-30 23:58 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  45. 2026-09-30 20:06 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  46. 2026-09-30 16:16 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  47. 2026-09-30 12:26 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  48. 2026-09-30 08:36 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  49. 2026-09-30 04:46 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  50. 2026-09-30 00:56 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  51. 2026-09-29 21:06 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  52. 2026-09-29 17:13 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  53. 2026-09-29 13:23 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  54. 2026-09-29 09:30 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  55. 2026-09-29 05:41 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  56. 2026-09-29 01:51 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  57. 2026-09-28 22:01 UTCEG score recompute
  58. 2026-09-28 22:01 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  59. 2026-09-28 18:11 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  60. 2026-09-28 14:18 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  61. 2026-09-28 10:28 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  62. 2026-09-28 06:39 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  63. 2026-09-28 02:49 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  64. 2026-09-27 23:00 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  65. 2026-09-27 21:51 UTCCISA KEV update
  66. 2026-09-27 19:10 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  67. 2026-09-27 15:20 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  68. 2026-09-27 11:30 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  69. 2026-09-27 07:40 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  70. 2026-09-27 03:50 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  71. 2026-09-26 23:59 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  72. 2026-09-26 20:10 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  73. 2026-09-26 16:20 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  74. 2026-09-26 12:30 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8
  75. 2026-09-26 08:40 UTCGHSA enrichmentGHSA-p8wc-6g47-vh8j · GitHub severity HIGH · GitHub CVSS 9.8

Publicly available exploits

(9 references)

Public exploit code is referenced for this CVE (2 Metasploit modules, 2 Exploit-DB entries, 4 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. No release with the fix is confirmed, so defenders should restrict or isolate affected systems accordingly until one is applied.

  • Metasploitauxiliary/scanner/http/ms15_034_http_sys_memory_dump✓ verified
    Published Jun 23, 2015

    MS15-034 HTTP Protocol Stack Request Handling HTTP.SYS Memory Information Disclosure

    Open source ↗
  • Metasploitauxiliary/dos/http/ms15_034_ulonglongadd✓ verified
    Published Apr 15, 2015

    MS15-034 HTTP Protocol Stack Request Handling Denial-of-Service

    Open source ↗
  • Nucleihttp/cves/2015/CVE-2015-1635.yaml
    Published Feb 28, 2024

    Microsoft Windows 'HTTP.sys' - Remote Code Execution

    Open source ↗
  • GitHub PoCh3x0v3rl0rd/CVE-2015-1635-POC
    Published Jul 12, 2021
    Open source ↗
  • GitHub PoCaedoo/CVE-2015-1635-POC
    Published Jun 20, 2018

    MS15-034 HTTP.sys 远程执行代码检测脚本（MS15-034 HTTP.sys remote execution code poc script）

    Open source ↗
  • GitHub PoCtechnion/erlvulnscan
    Published May 4, 2015

    Concurrent network scanner for CVE-2015-1635

    Open source ↗
  • Exploit-DBEDB-36776
    Published Apr 16, 2015

    Microsoft Windows - 'HTTP.sys' HTTP Request Parsing Denial of Service (MS15-034)

    Open source ↗
  • GitHub PoCZx7ffa4512-Python/Project-CVE-2015-1635
    Published Apr 16, 2015

    CVE-2015-1635,MS15-034

    Open source ↗
  • Exploit-DBEDB-36773
    Published Apr 15, 2015

    Microsoft Windows - 'HTTP.sys' (PoC) (MS15-034)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2015-1635?
CVE-2015-1635 is a critical-severity vulnerability; its CVE record was published on April 14, 2015. HTTP.sys in Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8, Windows 8.1, and Windows Server 2012 Gold and R2 allows remote attackers to execute arbitrary code via crafted HTTP requests, aka "HTTP.sys Remote Code Execution Vulnerability."
When was the CVE record for CVE-2015-1635 published?
The CVE record for CVE-2015-1635 was published on April 14, 2015. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 22, 2026; the record at its source may have been updated since.
Is CVE-2015-1635 actively exploited?
Yes. CISA added CVE-2015-1635 to the Known Exploited Vulnerabilities catalog on February 10, 2022, affecting Microsoft HTTP.sys. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
What is the CVSS score of CVE-2015-1635?
CVE-2015-1635 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2015-1635?
CVE-2015-1635 affects Microsoft HTTP.sys.
How do I remediate CVE-2015-1635?
A fix for CVE-2015-1635 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2015-1635

Explore →

Is Your Infrastructure Affected by CVE-2015-1635?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs