Debian LinuxOperating system · Debian
CVE-2013-2905
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 SharedMemory::Create function in memory/shared_memory_posix.cc in Google Chrome before 29.0.1547.57 uses weak permissions under /dev/shm/, which allows attackers to obtain sensitive information via direct access to a POSIX shared-memory file.
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 SharedMemory::Create function in Google Chrome creates POSIX shared memory files in /dev/shm/ with weak permissions (world-readable), allowing any local user to read sensitive data from these shared memory segments.
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
<= 29.0.1547.56= 29.0.1547.0= 29.0.1547.1= 29.0.1547.2= 29.0.1547.3= 29.0.1547.4= 29.0.1547.5= 29.0.1547.7= 29.0.1547.8= 29.0.1547.9= 29.0.1547.10= 29.0.1547.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
- 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 installed Chrome versionRun 'google-chrome --version' or 'chromium --version' to get the installed browser versionAffected if Version is <= 29.0.1547.56 or matches any of the specific affected versions (29.0.1547.0 through 29.0.1547.11)
-
Examine shared memory file permissions in /dev/shmList files in /dev/shm/ and check their permissions using 'ls -la /dev/shm/'Affected if Files owned by the current user or system processes show world-readable permissions (e.g., -rw-rw-rw-) instead of restrictive permissions like -rw-------
-
Identify Chrome-related shared memory filesRun 'ls -la /dev/shm/*' and look for files with patterns like 'Chrome_' or similar process identifiers; use 'ps aux | grep chrome' to identify running Chrome processes and cross-reference with file timestampsAffected if Shared memory files created by Chrome processes exist with permissions allowing world read access (mode 0777 or similar)
The environment is affected if Google Chrome version 29.0.1547.56 or below (or any version 29.0.1547.0-29.0.1547.11) is installed AND shared memory files in /dev/shm/ are created with weak world-readable permissions.
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 29.0.1547.57 or later where the permissions were corrected to be restrictive (e.g., 0600).
Fix this in Debian Linux
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2905 — 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-2905 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