ChromeWeb browser · Google
CVE-2011-2825
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 13.0.782.215 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors involving custom fonts.
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 · moderate confidenceUse-after-free vulnerability in Google Chrome's font handling mechanism affecting versions prior to 13.0.782.215. The vulnerability is triggered through malicious custom fonts and allows remote attackers to cause denial of service or potentially achieve unspecified code execution 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
ChromeWeb browser
< 13.0.782.215
SafariWeb browser
< 5.1.4< 10.6< 5.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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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.
-
Check Google Chrome versionOpen Chrome and navigate to chrome://version, or click Help > About Google ChromeAffected if Version displayed is earlier than 13.0.782.215
-
Check Apple Safari versionOpen Safari and click Safari > About Safari, or check the version in Applications > Safari > Get InfoAffected if Version shown is earlier than 5.1.4
-
Check Apple iTunes versionOpen iTunes and go to Help > About iTunes, or right-click iTunes in Applications and select Get InfoAffected if Version number is less than 10.6
-
Check Apple iOS versionOn the device, go to Settings > General > About and view the Version fieldAffected if Version number is less than 5.1 (for example, 5.0.x or earlier)
-
Identify if custom fonts can be loadedReview whether users in your environment have the ability to install or load custom font files (for example, through document viewers, web browsing, or email attachments)Affected if Custom font loading is permitted and users could be persuaded to open malicious font files
You are affected if any of the installed software (Chrome, Safari, iTunes, or iOS) matches a version below the thresholds AND users can be tricked into loading malicious custom fonts.
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.
dbcve · scoped5.15.1.410.6
Update Google Chrome to version 13.0.782.215 or later to patch the use-after-free vulnerability in the font rendering subsystem.
Chrome 13.0.782.215 (or later); Safari 5.1.4 (or later); iTunes 10.6 (or later); iOS 5.1 (or later)
- 1. Open Google Chrome and navigate to the menu (three dots in top-right corner)
- 2. Click on 'Help' and then select 'About Google Chrome'
- 3. The browser will automatically check for updates
- 4. If an update is available, click 'Update Google Chrome'
- 5. Restart the browser to complete the installation
- 6. Verify the version by returning to 'About Google Chrome' and confirming version 13.0.782.215 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2825 — 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-2011-2825 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