CVE-2003-0190

MEDIUMCVSS v2 · 5.05.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.0 — v2 rates that MEDIUM (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:N/A:N. 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 76.8% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
5.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 77%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 77%CVSS v2: 5.0Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

OpenSSH-portable (OpenSSH) 3.6.1p1 and earlier with PAM support enabled immediately sends an error message when a user does not exist, which allows remote attackers to determine valid usernames via a timing attack.

CVSS v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0(low)
EG Risk
58(Track)
EG Risk 58/100SSVC: Track

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
Severity50% × 45%
Exploitation77% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
77%
EPSS %ILE
100%
KEV
Not listed

Published

May 12, 2003

Last Modified

June 16, 2026

References (20)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2003-07-29redhat
redhatpatch2003-07-29redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openssh—1:3.8.1p1-8.sarge.4—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssh—1:3.8.1p1-8.sarge.4—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssh—1:3.8.1p1-8.sarge.4—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssh—1:3.8.1p1-8.sarge.4—

Weakness Classification(1)

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

All Vendor Advisories

(2)

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 2× in last 7d / 5× 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-09-16 05:27 UTCOSV refresh
  2. 2026-09-12 14:54 UTCEPSS rescore
  3. 2026-09-10 09:23 UTCEPSS rescore
  4. 2026-08-30 01:13 UTCEPSS rescore
  5. 2026-08-28 03:47 UTCOSV refresh
  6. 2026-08-11 17:02 UTCOSV refresh
  7. 2026-07-26 17:17 UTCOSV refresh
  8. 2026-07-26 13:23 UTCEG score recompute▲ 5.00
  9. 2026-07-24 14:11 UTCEPSS rescore
  10. 2026-07-23 00:45 UTCEG score recompute
  11. 2026-07-23 00:26 UTCEG score recompute▼ 7.70
  12. 2026-07-22 23:49 UTCEG score recompute▲ 7.70
  13. 2026-07-22 21:29 UTCEG score recompute
  14. 2026-07-20 17:02 UTCEPSS rescore
  15. 2026-07-19 14:25 UTCEPSS rescore
  16. 2026-07-16 16:58 UTCEPSS rescore
  17. 2026-07-15 01:55 UTCEPSS rescore
  18. 2026-07-15 01:55 UTCEPSS rescore
  19. 2026-07-13 06:07 UTCEPSS rescore
  20. 2026-07-11 08:22 UTCEPSS rescore
  21. 2026-07-11 08:22 UTCEPSS rescore
  22. 2026-07-09 11:45 UTCOSV refresh
  23. 2026-06-28 14:02 UTCEPSS rescore
  24. 2026-06-28 04:52 UTCEPSS rescore
  25. 2026-06-27 03:04 UTCEPSS rescore
Show 47 more
  1. 2026-06-23 21:29 UTCEPSS rescore
  2. 2026-06-21 01:56 UTCEPSS rescore
  3. 2026-06-21 00:12 UTCOSV refresh
  4. 2026-06-17 17:49 UTCEPSS rescore
  5. 2026-06-17 17:49 UTCEPSS rescore
  6. 2026-06-16 17:49 UTCEPSS rescore
  7. 2026-06-16 17:49 UTCEPSS rescore
  8. 2026-06-15 17:43 UTCEPSS rescore
  9. 2026-06-14 23:13 UTCEPSS rescore
  10. 2026-06-14 23:13 UTCEPSS rescore
  11. 2026-06-13 22:56 UTCEPSS rescore
  12. 2026-06-12 23:08 UTCEPSS rescore
  13. 2026-06-11 13:55 UTCEPSS rescore
  14. 2026-06-10 22:13 UTCEPSS rescore
  15. 2026-06-10 13:17 UTCEPSS rescore
  16. 2026-06-07 15:21 UTCEPSS rescore
  17. 2026-06-06 13:44 UTCEPSS rescore
  18. 2026-06-06 13:44 UTCEPSS rescore
  19. 2026-06-06 13:44 UTCEPSS rescore
  20. 2026-06-05 22:43 UTCEPSS rescore
  21. 2026-06-05 22:43 UTCEPSS rescore
  22. 2026-06-04 13:09 UTCEPSS rescore
  23. 2026-06-02 20:10 UTCEPSS rescore
  24. 2026-06-01 13:49 UTCEPSS rescore
  25. 2026-06-01 13:49 UTCEPSS rescore
  26. 2026-05-31 22:28 UTCEPSS rescore
  27. 2026-05-31 17:38 UTCEG score recompute
  28. 2026-05-31 17:38 UTCVendor advisory
  29. 2026-05-31 17:38 UTCGHSA enrichment
  30. 2026-05-31 00:13 UTCEPSS rescore
  31. 2026-05-31 00:13 UTCEPSS rescore
  32. 2026-05-29 13:40 UTCEPSS rescore
  33. 2026-05-29 13:40 UTCEPSS rescore
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-27 13:37 UTCEPSS rescore
  38. 2026-05-26 07:16 UTCEPSS rescore
  39. 2026-05-26 07:16 UTCEPSS rescore
  40. 2026-05-24 16:42 UTCEPSS rescore
  41. 2026-05-22 21:15 UTCEPSS rescore
  42. 2026-05-22 09:07 UTCOSV refresh
  43. 2026-05-20 22:36 UTCEPSS rescore
  44. 2026-05-20 11:20 UTCEPSS rescore
  45. 2026-05-20 11:20 UTCEPSS rescore
  46. 2026-05-18 21:29 UTCEPSS rescore
  47. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (3 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-3303✓ verified
    First seen Feb 13, 2007

    Portable OpenSSH 3.6.1p-PAM/4.1-SuSE - Timing Attack

    Open source ↗
  • Exploit-DBEDB-26✓ verified
    First seen May 2, 2003

    OpenSSH/PAM 3.6.1p1 - 'gossh.sh' Remote Users Ident

    Open source ↗
  • Exploit-DBEDB-25✓ verified
    First seen Apr 30, 2003

    OpenSSH/PAM 3.6.1p1 - Remote Users Discovery Tool

    Open source ↗
  • Metasploitauxiliary/scanner/ssh/ssh_enumusers✓ verified
    First seen Jan 1, 2003

    SSH Username Enumeration

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(4)

What is CVE-2003-0190?
CVE-2003-0190 is a medium vulnerability published on May 12, 2003. OpenSSH-portable (OpenSSH) 3.6.1p1 and earlier with PAM support enabled immediately sends an error message when a user does not exist, which allows remote attackers to determine valid usernames via a timing attack.
When was CVE-2003-0190 disclosed?
CVE-2003-0190 was first published in the National Vulnerability Database on May 12, 2003, 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-2003-0190 actively exploited?
CVE-2003-0190 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 77% probability of exploitation in the next 30 days, which ranks it in the top 0.5% of all scored CVEs.
How do I remediate CVE-2003-0190?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2003-0190, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2003-0190

Explore →

Is Your Infrastructure Affected by CVE-2003-0190?

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

Start Free Scan →Browse All CVEs