Chrome OsOperating system · Google
CVE-2017-15400
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 · uneditedInsufficient restriction of IPP filters in CUPS in Google Chrome OS prior to 62.0.3202.74 allowed a remote attacker to execute a command with the same privileges as the cups daemon via a crafted PPD file, aka a printer zeroconfig CRLF issue.
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 confidenceInsufficient restriction of IPP filters in CUPS (Common Unix Printing System) on Google Chrome OS allowed remote attackers to execute arbitrary commands with cups daemon privileges via a crafted PPD (PostScript Printer Description) file. The vulnerability stems from improper validation of IPP filter input, likely involving CRLF injection in the printer zeroconfig functionality.
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
Chrome OsOperating system
< 62.0.3202.74CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 the operating systemConfirm the system is running Google Chrome OS (not a general Linux distribution with CUPS). This vulnerability is specific to Chrome OS and does not affect standard Linux CUPS installations.Affected if The system is Google Chrome OS and the version is below 62.0.3202.74
-
Check the Chrome OS versionNavigate to chrome://settings/help or use the command 'chromeos-version' in the terminal to determine the installed Chrome OS version.Affected if The installed version is lower than 62.0.3202.74 (e.g., 62.0.3202.73 or earlier)
-
Verify IPP printer support is enabledCheck if CUPS and IPP printing functionality is enabled on the device. On Chrome OS, printing features are typically managed through the print management interface in Settings > Advanced > Printing.Affected if IPP printing and CUPS support are enabled on the system
-
Confirm printer auto-discovery (zeroconfig) is activeExamine whether printer zeroconf/auto-discovery is enabled. This can be verified in the printing settings or by checking if the cups-daemon is configured to automatically discover network printers.Affected if Printer auto-discovery (zeroconfig) is enabled, allowing the device to automatically detect and connect to network printers
The user is affected if the system runs Google Chrome OS version below 62.0.3202.74 AND has IPP printing with printer auto-discovery enabled, as the exploit requires crafting a malicious PPD file through the zeroconfig functionality.
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 data62.0.3202.74
Upgrade Google Chrome OS to version 62.0.3202.74 or later to patch the CUPS IPP filter vulnerability. As a defense-in-depth measure, disable printer auto-discovery (zeroconfig) if not needed and restrict network access to printing services.
Fix this in Chrome Os
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15400 — 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-2017-15400 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