Chrome OsOperating system · Google
CVE-2013-0927
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 · uneditedGoogle Chrome OS before 26.0.1410.57 relies on a Pango pango-utils.c read_config implementation that loads the contents of the .pangorc file in the user's home directory, and the file referenced by the PANGO_RC_FILE environment variable, which allows attackers to bypass intended access restrictions via crafted configuration data.
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 confidenceGoogle Chrome OS before 26.0.1410.57 uses a vulnerable Pango library implementation where the pango-utils.c read_config function loads configuration from the user's .pangorc file and the PANGO_RC_FILE environment variable without proper validation. This allows attackers to inject crafted configuration data that can bypass intended security restrictions.
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
<= 26.0.1410.56= 26.0.1410.0= 26.0.1410.1= 26.0.1410.3= 26.0.1410.4= 26.0.1410.5= 26.0.1410.6= 26.0.1410.7= 26.0.1410.8= 26.0.1410.9= 26.0.1410.10= 26.0.1410.11CVSS 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.
-
Check Chrome OS versionOpen chrome://version in the Chrome browser or check the About Chrome OS dialog in system settings. Look for the version number in the format X.X.X.Affected if The version is 26.0.1410.56 or lower, or matches any of the affected versions listed (26.0.1410.0 through 26.0.1410.11).
-
Verify Pango library is in useThe Pango library is used for text rendering in Chrome OS. Check if applications that render text are functioning normally, as Pango handles internationalized text layout.Affected if Pango is actively used for text rendering on the system, which is the default state for Chrome OS.
-
Inspect user .pangorc fileCheck for the existence of a .pangorc file in the user's home directory using the file manager or ls command in the terminal.Affected if A .pangorc file exists in the user's home directory and contains configuration data.
-
Check PANGO_RC_FILE environment variableOpen a terminal and run 'echo $PANGO_RC_FILE' to see if this environment variable is set.Affected if The PANGO_RC_FILE environment variable is set and points to a configuration file.
You are affected if your Chrome OS version is 26.0.1410.56 or lower and you either have a .pangorc file in your home directory or the PANGO_RC_FILE environment variable is set, allowing potentially malicious configuration injection through the vulnerable Pango library.
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 Chrome OS to version 26.0.1410.57 or later which patches the Pango library to properly validate configuration file contents before loading, preventing arbitrary configuration injection attacks.
Fix this in Chrome Os
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0927 — 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-0927 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