CVE-2003-1567

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.5 from GitHub Security Advisory published 2022-04-29. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 25%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2009 — use a compensating control (WAF / firewall / segmentation) and check the vendor's advisory.

The undocumented TRACK method in Microsoft Internet Information Services (IIS) 5.0 returns the content of the original request in the body of the response, which makes it easier for remote attackers to steal cookies and authentication credentials, or bypass the HttpOnly protection mechanism, by using TRACK to read the contents of the HTTP headers that are returned in the response, a technique that is similar to cross-site tracing (XST) using HTTP TRACE.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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: No fix has been recorded since the CVE record was published in 2009. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and check the vendor's advisory for a fix.
EPSS PROB
25%
EPSS %ILE
97th
KEV
Not listed

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

No fix has been recorded since the CVE record was published in 2009. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and check the vendor's advisory for a fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

January 15, 2009

Last Modified

May 28, 2026

Advisory Details (3)

Auto-updated May 30, 2026
No fix on record since 2009. Sources: cert.
Web page
https://www.aqtronix.com/Advisories/AQ-2003-02.txt
CERT

VU#288308 - Microsoft Internet Information Server (IIS) vulnerable to cross-site scripting via HTTP TRACK method

http://www.kb.cert.org/vuls/id/288308
Web page
http://www.aqtronix.com/Advisories/AQ-2003-02.txt

Vendor Advisories for CVE-2003-1567(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 11× 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.

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. 14 repeat rows among the latest 76 are merged into the row they repeat.

  1. 2026-10-12 02:24 UTCEG score recompute
  2. 2026-10-11 13:37 UTCEPSS rescoreEPSS 25% · 97th percentile
  3. 2026-10-10 19:53 UTCEPSS rescoreEPSS 25% · 97th percentile
  4. 2026-10-09 19:58 UTCEPSS rescoreEPSS 25% · 97th percentile
  5. 2026-10-08 16:28 UTCEPSS rescoreEPSS 25% · 97th percentile
  6. 2026-10-07 23:35 UTCEPSS rescoreEPSS 25% · 97th percentile
  7. 2026-10-06 15:08 UTCEPSS rescoreEPSS 25% · 97th percentile
  8. 2026-10-05 17:36 UTCEPSS rescoreEPSS 25% · 97th percentile
  9. 2026-10-03 14:19 UTCEPSS rescoreEPSS 25% · 97th percentile
  10. 2026-09-29 02:39 UTCEG score recompute
  11. 2026-09-12 14:54 UTCEPSS rescoreEPSS 25% · 97th percentile
  12. 2026-09-10 09:23 UTCEPSS rescoreEPSS 25% · 97th percentile
  13. 2026-08-30 01:13 UTCEPSS rescoreEPSS 25% · 97th percentile
  14. 2026-07-25 14:11 UTCEPSS rescoreEPSS 25% · 97th percentile
  15. 2026-07-24 14:11 UTCEPSS rescoreEPSS 25% · 97th percentile
  16. 2026-07-23 00:45 UTCEG score recompute
  17. 2026-07-23 00:27 UTCEG score recompute
  18. 2026-07-22 23:50 UTCEG score recompute
  19. 2026-07-22 21:30 UTCEG score recompute
  20. 2026-07-20 17:02 UTCEPSS rescoreEPSS 25% · 97th percentile
  21. 2026-07-19 14:25 UTCEPSS rescoreEPSS 25% · 97th percentile
  22. 2026-07-18 09:59 UTCEPSS rescoreEPSS 25% · 97th percentile
  23. 2026-07-16 16:58 UTCEPSS rescoreEPSS 25% · 97th percentile
  24. 2026-07-13 06:07 UTCEPSS rescoreEPSS 25% · 97th percentile
  25. 2026-07-11 08:22 UTCEPSS rescoreEPSS 25% · 97th percentile
Show 37 more
  1. 2026-07-08 15:09 UTCEPSS rescoreEPSS 25% · 97th percentile
  2. 2026-07-06 02:19 UTCEPSS rescoreEPSS 25% · 97th percentile
  3. 2026-07-04 06:26 UTCEPSS rescoreEPSS 25% · 97th percentile
  4. 2026-07-02 14:00 UTCEPSS rescoreEPSS 25% · 97th percentile
  5. 2026-06-29 14:02 UTCEPSS rescoreEPSS 25% · 97th percentile
  6. 2026-06-28 14:02 UTCEPSS rescoreEPSS 25% · 97th percentile
  7. 2026-06-28 04:52 UTCEPSS rescoreEPSS 25% · 97th percentile
  8. 2026-06-27 03:04 UTCEPSS rescoreEPSS 25% · 97th percentile
  9. 2026-06-23 21:29 UTCEPSS rescoreEPSS 25% · 97th percentile
  10. 2026-06-22 14:22 UTCEPSS rescoreEPSS 25% · 97th percentile
  11. 2026-06-21 14:52 UTCEPSS rescoreEPSS 25% · 97th percentile
  12. 2026-06-21 01:56 UTCEPSS rescoreEPSS 25% · 97th percentile
  13. 2026-06-18 17:49 UTCEPSS rescoreEPSS 25% · 97th percentile
  14. 2026-06-17 17:49 UTCEPSS rescoreEPSS 25% · 97th percentile
  15. 2026-06-16 17:49 UTCEPSS rescoreEPSS 25% · 97th percentile
  16. 2026-06-15 17:43 UTCEPSS rescoreEPSS 25% · 97th percentile
  17. 2026-06-14 23:13 UTCEPSS rescoreEPSS 80% · 99th percentile
  18. 2026-06-12 23:08 UTCEPSS rescoreEPSS 80% · 99th percentile
  19. 2026-06-10 22:13 UTCEPSS rescoreEPSS 80% · 99th percentile
  20. 2026-06-10 13:17 UTCEPSS rescoreEPSS 80% · 99th percentile
  21. 2026-06-08 14:13 UTCEPSS rescoreEPSS 80% · 99th percentile
  22. 2026-06-07 15:21 UTCEPSS rescoreEPSS 80% · 99th percentile
  23. 2026-06-06 13:44 UTCEPSS rescoreEPSS 80% · 99th percentile
  24. 2026-06-05 22:43 UTCEPSS rescoreEPSS 80% · 99th percentile
  25. 2026-06-05 06:07 UTCEPSS rescoreEPSS 67% · 98th percentile
  26. 2026-06-04 13:09 UTCEPSS rescoreEPSS 67% · 98th percentile
  27. 2026-06-02 20:10 UTCEPSS rescoreEPSS 67% · 98th percentile
  28. 2026-06-01 13:49 UTCEPSS rescoreEPSS 67% · 98th percentile
  29. 2026-05-31 22:28 UTCEPSS rescoreEPSS 67% · 98th percentile
  30. 2026-05-31 00:13 UTCEPSS rescoreEPSS 67% · 98th percentile
  31. 2026-05-30 18:45 UTCEG score recompute
  32. 2026-05-30 18:45 UTCGHSA enrichmentGHSA-52vj-29px-76m7 · GitHub CVSS 7.5
  33. 2026-05-29 13:40 UTCEPSS rescoreEPSS 67% · 98th percentile
  34. 2026-05-27 13:37 UTCEPSS rescoreEPSS 69% · 98th percentile
  35. 2026-05-22 21:15 UTCEPSS rescoreEPSS 69% · 98th percentile
  36. 2026-05-20 22:36 UTCEPSS rescoreEPSS 69% · 98th percentile
  37. 2026-05-18 21:29 UTCEPSS rescoreEPSS 69% · 98th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2003-1567?
CVE-2003-1567 is a high-severity vulnerability; its CVE record was published on January 15, 2009. The undocumented TRACK method in Microsoft Internet Information Services (IIS) 5.0 returns the content of the original request in the body of the response, which makes it easier for remote attackers to steal cookies and authentication credentials, or bypass the HttpOnly protection mechanism, by…
When was the CVE record for CVE-2003-1567 published?
The CVE record for CVE-2003-1567 was published on January 15, 2009. 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 May 28, 2026; the record at its source may have been updated since.
Is CVE-2003-1567 actively exploited?
CVE-2003-1567 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2003-1567?
CVE-2003-1567 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2003-1567?
No fix for CVE-2003-1567 has been recorded since its CVE record was published in 2009. Restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and check the vendor's advisory for a fix. The vendor advisories EchelonGraph has for CVE-2003-1567 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2003-1567

Explore →

Is Your Infrastructure Affected by CVE-2003-1567?

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

Book a Demo →Browse All CVEs