CVE-2015-8560
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 · uneditedIncomplete blacklist vulnerability in util.c in foomatic-rip in cups-filters 1.0.42 before 1.4.0 and in foomatic-filters in Foomatic 4.0.x allows remote attackers to execute arbitrary commands via a ; (semicolon) character in a print job, a different vulnerability than CVE-2015-8327.
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 confidenceIncomplete blacklist vulnerability in util.c within foomatic-rip (cups-filters) and foomatic-filters allows remote attackers to execute arbitrary commands through print jobs by injecting a semicolon (;) character, bypassing input validation.
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= 12.04= 14.04= 15.04= 15.10= 8.0= 1.0.42= 1.0.43= 1.0.44= 1.0.45= 1.0.46= 1.0.47= 1.0.48= 1.0.49= 1.0.50= 1.0.51= 1.0.52= 1.0.53= 4.0.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 4.0.8= 4.0.9= 4.0.10= 4.0.11CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed cups-filters versionRun 'dpkg -l cups-filters' on Debian/Ubuntu or 'rpm -q cups-filters' on RPM-based systems to list the installed package versionAffected if The version listed is between 1.0.42 and 1.0.53 inclusive
-
Identify installed foomatic-filters versionRun 'dpkg -l foomatic-filters' on Debian/Ubuntu or 'rpm -q foomatic-filters' on RPM-based systems to list the installed package versionAffected if The version listed is between 4.0.0 and 4.0.11 inclusive
-
Verify foomatic-rip is in useCheck if CUPS is running ('systemctl status cups' or 'service cups status') and examine printer configuration files in /etc/cups/ to confirm foomatic-rip is the filter being used for any configured printersAffected if CUPS is active and printers are configured to use foomatic-rip as the raster filter or rip handler
-
Confirm print job submission is accessibleCheck if the CUPS web interface is bound to network interfaces ('Listen' or 'Port' directives in /etc/cups/cupsd.conf) or if anonymous print access is permitted in /etc/cups/printers.confAffected if CUPS is listening on a network interface or allows print jobs from untrusted sources
You are affected if you have cups-filters versions 1.0.42-1.0.53 or foomatic-filters versions 4.0.0-4.0.11 installed with CUPS running and foomatic-rip actively handling print jobs from accessible sources.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to cups-filters 1.4.0+ or Foomatic 4.0.x patched versions; alternatively, isolate print services in a restricted network segment and disable unnecessary print job submission interfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8560 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-8560 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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