CVE-2011-4328
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 · uneditedplugin/npapi/plugin.cpp in Gnash before 0.8.10 uses weak permissions (world readable) for cookie files with predictable names in /tmp, which allows local users to obtain sensitive information.
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 Gnash NPAPI plugin creates cookie files in /tmp with world-readable permissions (0644) and predictable filenames, allowing any local user to read potentially sensitive cookie data belonging to other users by knowing or guessing the file names.
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<= 0.8.9= 0.8.5= 0.8.7= 0.8.8= 0.8.9CVSS 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.
-
Check if Gnash is installedRun 'gnash --version' or check package manager for gnash packageAffected if Gnash version is 0.8.5, 0.8.7, 0.8.8, or any version <= 0.8.9
-
Check if NPAPI plugin is presentLook for libgnashplugin.so in browser plugin directories (e.g., /usr/lib/mozilla/plugins/, ~/.mozilla/plugins/)Affected if The NPAPI plugin file exists in browser plugin directories
-
Find cookie files created by Gnash in /tmpList files in /tmp matching Gnash cookie pattern (typically starting with 'gnash_cookie' or similar naming convention)Affected if Cookie files exist in /tmp directory
-
Verify cookie file permissions are world-readableRun 'ls -la /tmp/gnash*' or check specific cookie file permissions using 'stat -c %a <filename>'Affected if Cookie files have 0644 permissions (world-readable)
A system is affected if Gnash version 0.8.5-0.8.9 with NPAPI plugin is installed and creates cookie files in /tmp with 0644 (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 dataModify the file creation code in plugin/npapi/plugin.cpp to set restrictive permissions (0600) on cookie files, preventing unauthorized local access.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4328 — 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-4328 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