CVE-2004-0411

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 7.8% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 7.8%CVSS v2: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The URI handlers in Konqueror for KDE 3.2.2 and earlier do not properly filter "-" characters that begin a hostname in a (1) telnet, (2) rlogin, (3) ssh, or (4) mailto URI, which allows remote attackers to manipulate the options that are passed to the associated programs, possibly to read arbitrary files or execute arbitrary code.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5HIGHlow confidence
EG Risk
41
EG Risk 41/100CISA SSVC

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
Severity75% × 45%
Exploitation8% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
7.8%
EPSS %ILE
94th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 7, 2004

Last Modified

June 16, 2026

References (34)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpatch2004-05-17redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:3.0(1)
PackageVulnerable rangeFix by version rangeDependents
kdelibs—
  • every version up to 4:2.2.2-13.woody.10: fixed in 4:2.2.2-13.woody.10
—

Weakness Classification(2)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-09 19:58 UTCEPSS rescore
  2. 2026-10-08 16:28 UTCEPSS rescore
  3. 2026-10-07 23:35 UTCEPSS rescore
  4. 2026-10-06 15:08 UTCEPSS rescore
  5. 2026-10-05 17:36 UTCEPSS rescore
  6. 2026-10-04 23:15 UTCEPSS rescore
  7. 2026-10-03 14:19 UTCEPSS rescore
  8. 2026-09-29 02:39 UTCEG score recompute
  9. 2026-09-12 14:54 UTCEPSS rescore
  10. 2026-09-10 09:23 UTCEPSS rescore
  11. 2026-08-30 01:13 UTCEPSS rescore
  12. 2026-07-26 13:24 UTCEG score recompute▲ 7.50
  13. 2026-07-25 14:11 UTCEPSS rescore
  14. 2026-07-24 14:11 UTCEPSS rescore
  15. 2026-07-23 00:45 UTCEG score recompute
  16. 2026-07-23 00:27 UTCEG score recompute
  17. 2026-07-22 23:50 UTCEG score recompute
  18. 2026-07-22 21:30 UTCEG score recompute
  19. 2026-07-20 17:02 UTCEPSS rescore
  20. 2026-07-19 14:25 UTCEPSS rescore
  21. 2026-07-18 09:59 UTCEPSS rescore
  22. 2026-07-18 09:59 UTCEPSS rescore
  23. 2026-07-16 16:58 UTCEPSS rescore
  24. 2026-07-15 01:55 UTCEPSS rescore
  25. 2026-07-15 01:55 UTCEPSS rescore
Show 62 more
  1. 2026-07-11 08:22 UTCEPSS rescore
  2. 2026-07-11 08:22 UTCEPSS rescore
  3. 2026-07-08 15:09 UTCEPSS rescore
  4. 2026-07-06 02:19 UTCEPSS rescore
  5. 2026-07-04 06:26 UTCEPSS rescore
  6. 2026-07-02 14:00 UTCEPSS rescore
  7. 2026-06-29 14:02 UTCEPSS rescore
  8. 2026-06-29 14:02 UTCEPSS rescore
  9. 2026-06-28 14:02 UTCEPSS rescore
  10. 2026-06-28 04:52 UTCEPSS rescore
  11. 2026-06-27 03:04 UTCEPSS rescore
  12. 2026-06-23 21:29 UTCEPSS rescore
  13. 2026-06-22 14:22 UTCEPSS rescore
  14. 2026-06-21 14:52 UTCEPSS rescore
  15. 2026-06-21 01:56 UTCEPSS rescore
  16. 2026-06-18 17:49 UTCEPSS rescore
  17. 2026-06-18 17:49 UTCEPSS rescore
  18. 2026-06-17 17:49 UTCEPSS rescore
  19. 2026-06-17 17:49 UTCEPSS rescore
  20. 2026-06-16 17:49 UTCEPSS rescore
  21. 2026-06-16 17:49 UTCEPSS rescore
  22. 2026-06-15 17:43 UTCEPSS rescore
  23. 2026-06-14 23:13 UTCEPSS rescore
  24. 2026-06-14 23:13 UTCEPSS rescore
  25. 2026-06-13 22:56 UTCEPSS rescore
  26. 2026-06-12 23:08 UTCEPSS rescore
  27. 2026-06-11 13:55 UTCEPSS rescore
  28. 2026-06-10 22:13 UTCEPSS rescore
  29. 2026-06-10 13:17 UTCEPSS rescore
  30. 2026-06-08 14:13 UTCEPSS rescore
  31. 2026-06-07 15:21 UTCEPSS rescore
  32. 2026-06-06 13:44 UTCEPSS rescore
  33. 2026-06-06 13:44 UTCEPSS rescore
  34. 2026-06-06 13:44 UTCEPSS rescore
  35. 2026-06-05 22:43 UTCEPSS rescore
  36. 2026-06-05 22:43 UTCEPSS rescore
  37. 2026-06-05 06:07 UTCEPSS rescore
  38. 2026-06-04 13:09 UTCEPSS rescore
  39. 2026-06-02 20:10 UTCEPSS rescore
  40. 2026-06-01 13:49 UTCEPSS rescore
  41. 2026-06-01 13:49 UTCEPSS rescore
  42. 2026-05-31 22:28 UTCEPSS rescore
  43. 2026-05-31 16:15 UTCEG score recompute
  44. 2026-05-31 16:15 UTCVendor advisory
  45. 2026-05-31 16:15 UTCGHSA enrichment
  46. 2026-05-31 00:13 UTCEPSS rescore
  47. 2026-05-31 00:13 UTCEPSS rescore
  48. 2026-05-29 13:40 UTCEPSS rescore
  49. 2026-05-29 13:40 UTCEPSS rescore
  50. 2026-05-28 13:42 UTCEPSS rescore
  51. 2026-05-28 13:42 UTCEPSS rescore
  52. 2026-05-28 13:42 UTCEPSS rescore
  53. 2026-05-27 13:37 UTCEPSS rescore
  54. 2026-05-26 13:41 UTCEPSS rescore
  55. 2026-05-26 13:41 UTCEPSS rescore
  56. 2026-05-24 16:42 UTCEPSS rescore
  57. 2026-05-22 21:15 UTCEPSS rescore
  58. 2026-05-20 22:36 UTCEPSS rescore
  59. 2026-05-20 11:20 UTCEPSS rescore
  60. 2026-05-20 11:20 UTCEPSS rescore
  61. 2026-05-18 21:29 UTCEPSS rescore
  62. 2026-05-18 21:29 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(4)

What is CVE-2004-0411?
CVE-2004-0411 is a high vulnerability published on July 7, 2004. The URI handlers in Konqueror for KDE 3.2.2 and earlier do not properly filter "-" characters that begin a hostname in a (1) telnet, (2) rlogin, (3) ssh, or (4) mailto URI, which allows remote attackers to manipulate the options that are passed to the associated programs, possibly to read arbitrary…
When was CVE-2004-0411 disclosed?
CVE-2004-0411 was first published on July 7, 2004, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2004-0411 actively exploited?
CVE-2004-0411 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.8% probability of exploitation in the next 30 days (94th percentile of EPSS-scored CVEs).
How do I remediate CVE-2004-0411?
A fix for CVE-2004-0411 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2004-0411

Explore →

Is Your Infrastructure Affected by CVE-2004-0411?

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

Book a Demo →Browse All CVEs