CVE-2005-4145

MEDIUMCVSS v2 · 6.56.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 6.5 — 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:S/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 43.9% 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
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 44%CVSS v2: 6.5Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The MSDE version of Lyris ListManager 5.0 through 8.9b configures the sa account in the database to use a password with a small search space ("lyris" and up to 5 digits, possibly from the process ID), which allows remote attackers to gain access via a brute force attack.

CVSS v2.0 (legacy)
6.5MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
6.5(low)
EG Risk
60(Track)
EG Risk 60/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
Severity65% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
44%
EPSS %ILE
99%
KEV
Not listed

Published

December 10, 2005

Last Modified

April 16, 2026

References (12)

Data Freshness Timeline

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

Publicly available exploits

(2 references)

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

  • Exploit-DBEDB-16397✓ verified
    First seen Sep 20, 2010

    Lyris ListManager - MSDE Weak sa Password (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/mssql/lyris_listmanager_weak_pass✓ verified
    First seen Dec 8, 2005

    Lyris ListManager MSDE Weak sa Password

    Open source ↗

Frequently asked(4)

What is CVE-2005-4145?
CVE-2005-4145 is a medium vulnerability published on December 10, 2005. The MSDE version of Lyris ListManager 5.0 through 8.9b configures the sa account in the database to use a password with a small search space ("lyris" and up to 5 digits, possibly from the process ID), which allows remote attackers to gain access via a brute force attack.
When was CVE-2005-4145 disclosed?
CVE-2005-4145 was first published in the National Vulnerability Database on December 10, 2005, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2005-4145 actively exploited?
CVE-2005-4145 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 44% probability of exploitation in the next 30 days, which ranks it in the top 1.3% of all scored CVEs.
How do I remediate CVE-2005-4145?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-4145, 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

Explore the affected products and dependency analysis for CVE-2005-4145

Explore →

Is Your Infrastructure Affected by CVE-2005-4145?

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

Start Free Scan →Browse All CVEs