Debian LinuxOperating system · Debian
CVE-2013-2927
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 the HTMLFormElement::prepareForSubmission function in core/html/HTMLFormElement.cpp in Blink, as used in Google Chrome before 30.0.1599.101, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to submission for FORM elements.
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 confidenceA use-after-free vulnerability exists in the HTMLFormElement::prepareForSubmission function in Blink (the rendering engine used by Google Chrome). When processing FORM element submissions, memory is freed but still referenced, allowing attackers to potentially execute arbitrary code or cause a denial of service by triggering the vulnerability through specially crafted web pages.
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= 8.0
ChromeWeb browser
<= 30.0.1599.100= 30.0.1599.0= 30.0.1599.1= 30.0.1599.2= 30.0.1599.4= 30.0.1599.5= 30.0.1599.6= 30.0.1599.7= 30.0.1599.8= 30.0.1599.9= 30.0.1599.10= 30.0.1599.11= 12.2= 12.3= 13.1CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Identify installed Google Chrome versionOpen Chrome, click the menu icon (three dots) > Help > About Google Chrome, or navigate to chrome://settings/helpAffected if The displayed version is 30.0.1599.100 or earlier, or exactly matches any of these versions: 30.0.1599.0, 30.0.1599.1, 30.0.1599.2, 30.0.1599.4, 30.0.1599.5, 30.0.1599.6, 30.0.1599.7, 30.0.1599.8, 30.0.1599.9, 30.0.1599.10, or 30.0.1599.11
-
Check Chrome version via command line (if available)Run 'google-chrome --version' or 'chromium --version' in a terminalAffected if The output shows a version number that falls within the affected ranges described above
-
Verify on Linux systems with package managerOn Debian-based systems run 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable'; on OpenSUSE run 'rpm -qi chromium' or 'zypper info chromium'Affected if The installed package version matches any of the affected Chrome versions listed for Debian (7.0, 8.0) or OpenSUSE (12.2, 12.3, 13.1) with vulnerable Chrome versions
A system is affected if Google Chrome version is 30.0.1599.100 or earlier, or exactly matches any of the specific vulnerable versions (30.0.1599.0 through 30.0.1599.11).
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 Google Chrome to version 30.0.1599.101 or later. Organizations should deploy browser updates via 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-2927 — 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-2927 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