dbcve.org
CupsApplication

CVE-2008-0882

HIGH · 10.0 CVSS v2.0 Published 2008-02-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Double free vulnerability in the process_browse_data function in CUPS 1.3.5 allows remote attackers to cause a denial of service (daemon crash) and possibly execute arbitrary code via crafted UDP Browse packets to the cupsd port (631/udp), related to an unspecified manipulation of a remote printer. NOTE: some of these details are obtained from third party information.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A double-free vulnerability exists in the process_browse_data function of CUPS 1.3.5, where crafted UDP Browse packets sent to port 631/UDP can trigger a double-free condition. This allows remote attackers to crash the cupsd daemon and potentially execute arbitrary code through unspecified manipulation of a remote printer.

MitigationUpgrade CUPS to a patched version beyond 1.3.5. If immediate patching is not feasible, consider blocking UDP port 631 at network boundaries or disabling CUPS browser browsing functionality to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CupsApplication
Affected:= 1.3.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify CUPS version
    Run 'cups-config --version' or check the package manager (e.g., 'dpkg -l cups', 'rpm -q cups', or 'yum list installed cups') to determine the installed CUPS version
    Affected if The installed version is exactly 1.3.5
  2. Verify cupsd daemon is running
    Run 'ps aux | grep cupsd' or 'systemctl status cups' (or 'service cups status' on older systems) to check if the CUPS daemon is active
    Affected if cupsd is running and the CUPS version is 1.3.5
  3. Confirm UDP port 631 is listening
    Run 'netstat -uan | grep 631' or 'ss -uan | grep 631' to check if the CUPS UDP Browse port is open
    Affected if Port 631/UDP is open and CUPS version is 1.3.5
  4. Check if CUPS browser browsing is enabled
    Inspect the CUPS configuration file /etc/cups/cupsd.conf for 'BrowseProtocols', 'BrowseAddress', or 'Browsing On' directives. Alternatively, run 'lpoptions -p <printer> -l' to list printer options. The browse daemon listens for UDP packets when browsing is enabled.
    Affected if CUPS browser browsing functionality is enabled (Browsing On in cupsd.conf) and the version is 1.3.5

A system is affected if it runs CUPS version 1.3.5 with the cupsd daemon active, UDP port 631 open, and CUPS browser browsing functionality enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade CUPS to a patched version beyond 1.3.5. If immediate patching is not feasible, consider blocking UDP port 631 at network boundaries or disabling CUPS browser browsing functionality to reduce attack surface.

Recommended fix High confidence

CUPS 1.3.6 or later (or latest stable version available from your distribution vendor)

  1. 1. Identify the CUPS package manager for your system (apt, yum, zypper, etc.)
  2. 2. Back up your current CUPS configuration (/etc/cups/ directory)
  3. 3. Update the package repository metadata
  4. 4. Upgrade the cups package to version 1.3.6 or later, or to the latest stable version available for your distribution
  5. 5. Restart the CUPS daemon: service cups restart or systemctl restart cups
  6. 6. Verify the CUPS version running: cupsd --version
  7. 7. Test that printing functionality works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cups Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-0882 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-0882 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data