Debian LinuxOperating system · Debian
CVE-2013-2885
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 · uneditedUse-after-free vulnerability in Google Chrome before 28.0.1500.95 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to not properly considering focus during the processing of JavaScript events in the presence of a multiple-fields input type.
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 confidenceUse-after-free vulnerability in Google Chrome (versions before 28.0.1500.95) where the browser fails to properly handle focus during JavaScript event processing with multiple-fields input types (e.g., email, datetime inputs). This allows remote attackers to potentially execute arbitrary code or cause denial of service by freeing memory that is still referenced.
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
Debian LinuxOperating system
= 7.0
ChromeWeb browser
<= 28.0.1500.94= 28.0.1500.0= 28.0.1500.2= 28.0.1500.3= 28.0.1500.4= 28.0.1500.5= 28.0.1500.6= 28.0.1500.8= 28.0.1500.9= 28.0.1500.10= 28.0.1500.11= 28.0.1500.12CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Determine installed Google Chrome versionNavigate to chrome://version in the browser address bar or click Help > About Google ChromeAffected if The displayed version is 28.0.1500.94 or lower, or matches any of the specific affected versions listed (28.0.1500.0 through 28.0.1500.12)
-
Verify Chrome version on Debian systemsOn Debian 7.0 systems, use the package manager command: dpkg -l | grep google-chrome or check the installed package versionAffected if Google Chrome package version corresponds to an affected 28.0.1500.x release
-
Confirm browser is actively usedDetermine if Chrome is the primary or commonly used browser in the environmentAffected if Users actively use the affected Chrome version to browse web content
You are affected if Google Chrome version 28.0.1500.94 or any version from 28.0.1500.0 through 28.0.1500.12 is installed and actively used, as the use-after-free flaw in focus handling during JavaScript event processing with multi-field input types can be triggered by malicious web pages.
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 28.0.1500.95 or later. Organizations should deploy browser updates through their patch management systems and verify completion across all endpoints.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2885 — 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-2013-2885 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