Enterprise Linux Desktop SupplementaryOperating system · Redhat
CVE-2015-1285
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 · uneditedThe XSSAuditor::canonicalize function in core/html/parser/XSSAuditor.cpp in the XSS auditor in Blink, as used in Google Chrome before 44.0.2403.89, does not properly choose a truncation point, which makes it easier for remote attackers to obtain sensitive information via an unspecified linear-time attack.
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 confidenceThe XSSAuditor::canonicalize function in Blink's XSS auditor does not properly select a truncation point when canonicalizing HTML. This flawed logic enables a linear-time attack that can potentially expose sensitive information through the XSS auditor's behavior, rather than executing XSS payloads directly.
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
Enterprise Linux Desktop SupplementaryOperating system
= 6.0
Enterprise Linux Server SupplementaryOperating system
= 6.0
Enterprise Linux Server Supplementary EusOperating system
= 6.7z
Enterprise Linux Workstation SupplementaryOperating system
= 6.0
Debian LinuxOperating system
= 8.0
ChromeWeb browser
<= 43.0.2357.134= 13.1= 13.2CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 Chrome browser versionOpen Chrome, navigate to chrome://version, or go to Settings > About Chrome to view the installed version numberAffected if The installed version is 43.0.2357.134 or earlier
-
Check Chromium on Red Hat systemsOn RHEL systems, run 'rpm -q chromium' or 'google-chrome --version' to determine the installed browser versionAffected if Chromium or Google Chrome version is 43.0.2357.134 or earlier
-
Check Chromium on Debian systemsOn Debian systems, run 'dpkg -l | grep chromium' or 'google-chrome --version' to list installed browser packages and versionsAffected if Chromium or Google Chrome version is 43.0.2357.134 or earlier
-
Check browser on OpenSUSE systemsOn OpenSUSE systems, run 'rpm -q chromium' or 'google-chrome --version' to identify installed browser packagesAffected if Chromium or Google Chrome version is 43.0.2357.134 or earlier
If the installed Chrome or Chromium browser version is 43.0.2357.134 or earlier on any supported platform, the XSSAuditor vulnerability is present in that environment.
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 dataUpdate Google Chrome to version 44.0.2403.89 or later to obtain the patched XSSAuditor. No web application changes are required as this is a browser-side vulnerability.
Fix this in Enterprise Linux Desktop Supplementary
Scoped from the published advisory
- Consultation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1285 — 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-1285 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