CVE-2009-0949

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
7.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, public exploit)
CISA-KEV: Not listedEPSS PROB: 20%CVSS: 7.5Exploit: Exploit-DB (verified) · epss top5pct · public exploitExposed services: Not assessed

A fix is available — apply it.

The ippReadIO function in cups/ipp.c in cupsd in CUPS before 1.3.10 does not properly initialize memory for IPP request packets, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via a scheduler request with two consecutive IPP_TAG_UNSUPPORTED tags.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
64
EG Risk 64/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%
Exploitation65% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; 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
20%
EPSS %ILE
97th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; 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 public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). 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

June 9, 2009

Last Modified

April 23, 2026

Advisory Details (7)

Auto-updated May 30, 2026
Patch available.
generic
http://securitytracker.com/id?1022321
generic

About Secunia Research | Flexera

http://secunia.com/advisories/36701
generic

About Secunia Research | Flexera

http://secunia.com/advisories/35685
generic

About Secunia Research | Flexera

http://secunia.com/advisories/35342
generic

About Secunia Research | Flexera

http://secunia.com/advisories/35340
generic

About Secunia Research | Flexera

http://secunia.com/advisories/35328
generic

About Secunia Research | Flexera

http://secunia.com/advisories/35322

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntucups (1.3.9-17ubuntu3.1) @ jaunty2026-05-30ubuntu
redhatcups-1:1.1.22-0.rc1.9.32.el4_8.32009-06-03redhat
redhatcups-1:1.3.7-8.el5_3.62009-06-03redhat

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

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
cups—
  • every version up to 1.3.10-1: fixed in 1.3.10-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
cups—
  • every version up to 1.3.10-1: fixed in 1.3.10-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
cups—
  • every version up to 1.3.10-1: fixed in 1.3.10-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
cups—
  • every version up to 1.3.10-1: fixed in 1.3.10-1
—
Debian:4.0(1)
PackageVulnerable rangeFix by version rangeDependents
cupsys1.2.7-4 ... 1.2.7-4etch7 (8 versions)
  • every version up to 1.2.7-4+etch8: fixed in 1.2.7-4+etch8
—
Debian:5.0(1)
PackageVulnerable rangeFix by version rangeDependents
cups1.3.8-1lenny4.1, 1.3.8-1lenny5
  • every version up to 1.3.8-1+lenny6: fixed in 1.3.8-1+lenny6
—

Weakness Classification(2)

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

All Vendor Advisories

(3)

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 5× in last 7d / 16× 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.

Showing the most recent 100 of 125 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-33020✓ verified
    First seen Jun 2, 2009

    CUPS 1.3.9 - 'cups/ipp.c' Null Pointer Dereference Denial of Service

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Same vendor

2 shown

redhat:RHSA-2009:1083

Frequently asked(5)

What is CVE-2009-0949?
CVE-2009-0949 is a high vulnerability published on June 9, 2009. The ippReadIO function in cups/ipp.c in cupsd in CUPS before 1.3.10 does not properly initialize memory for IPP request packets, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via a scheduler request with two consecutive IPPTAGUNSUPPORTED tags.
When was CVE-2009-0949 disclosed?
CVE-2009-0949 was first published on June 9, 2009, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2009-0949 actively exploited?
CVE-2009-0949 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 20% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2009-0949?
CVE-2009-0949 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2009-0949?
A fix for CVE-2009-0949 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-2009-0949

Explore →

Is Your Infrastructure Affected by CVE-2009-0949?

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

Book a Demo →Browse All CVEs