Foo2zjsApplication · Rkkda
CVE-2011-2684
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 · uneditedfoo2zjs before 20110722dfsg-3ubuntu1 as packaged in Ubuntu, 20110722dfsg-1 as packaged in Debian unstable, and 20090908dfsg-5.1+squeeze0 as packaged in Debian squeeze create temporary files insecurely, which allows local users to write over arbitrary files via a symlink attack on /tmp/foo2zjs.
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 confidencefoo2zjs printer driver creates temporary files in /tmp with predictable names without proper checks, allowing local users to perform a symlink attack and overwrite arbitrary files on the system.
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
Foo2zjsApplication
= 20090908dfsg-5.1\+squeeze0= 20110722dfsg-1= 20110722dfsg-3ubuntu1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 if foo2zjs is installedRun 'dpkg -l | grep foo2zjs' on Debian/Ubuntu systems, or 'rpm -qa | grep foo2zjs' on RPM-based systems, or check for the package via your system's package managerAffected if foo2zjs package is found on the system
-
Retrieve the installed version numberRun 'dpkg -s foo2zjs' on Debian/Ubuntu or 'rpm -qi foo2zjs' on RPM-based systems to obtain the exact version stringAffected if The installed version matches exactly 20090908dfsg-5.1+squeeze0, 20110722dfsg-1, or 20110722dfsg-3ubuntu1
-
Check for vulnerable temporary file usageReview the foo2zjs printer driver scripts (typically in /usr/bin or /usr/lib/cups/backend) for code that creates temporary files in /tmp using predictable names or the mktemp command without proper safeguardsAffected if The driver creates temporary files in /tmp with predictable filenames rather than using secure methods like mkstemp or a private temp directory
-
Verify if CUPS print queue uses foo2zjsRun 'lpstat -v' to list available print devices and check if any queue is configured using foo2zjs as the driver (often identified in printer URI or device/PPD configuration)Affected if A CUPS print queue is actively using the foo2zjs driver
A system is affected only if foo2zjs is installed and the exact version matches one of the three vulnerable releases (20090908dfsg-5.1+squeeze0, 20110722dfsg-1, or 20110722dfsg-3ubuntu1) AND the printer driver is in active use.
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 foo2zjs to version 20110722dfsg-3ubuntu1 (Ubuntu), 20110722dfsg-1 (Debian unstable), or 20090908dfsg-5.1+squeeze0 (Debian squeeze) which contain the secure temporary file handling fix.
Fix this in Foo2zjs
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-2011-2684 — 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-2684 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