CVE-2008-0930
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 · uneditedw_editeur.c in XWine 1.0.1 for Debian GNU/Linux allows local users to overwrite or print arbitrary files via a symlink attack on the temporaire temporary file. NOTE: some of these details are obtained from third party 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 · moderate confidenceA symlink attack vulnerability exists in XWine 1.0.1 where w_editeur.c creates a temporary file named 'temporaire' in a predictable location without proper checks. Local attackers can exploit this by creating a symbolic link at the expected temp file path before the application runs, causing the application to overwrite or print arbitrary files when it attempts to write to or use the 'temporaire' file.
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= 1.0.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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/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 XWine versionRun 'xwine --version' or check the installed package version using your system's package manager (e.g., 'dpkg -l | grep xwine', 'rpm -qi xwine', or 'ls /usr/bin/xwine')Affected if The installed version is exactly 1.0.1 from Freshmeat repository
-
Locate the w_editeur componentSearch for the w_editeur.c source file or compiled binary within the XWine installation directory, typically found under /usr/share/xwine or /usr/local/xwineAffected if The w_editeur component exists and is part of the installed XWine package
-
Identify temp file creation in w_editeurExamine the XWine binary or source code for references to a file named 'temporaire' being created in a predictable location (check for open() or fopen() calls with 'temporaire' without O_EXCL flag)Affected if The code creates a file named 'temporaire' without O_EXCL or mkstemp() security measures
-
Check for symlink vulnerability exposureVerify if the directory where 'temporaire' is created is writable by untrusted local users (common locations include /tmp, /var/tmp, or the user's home directory)Affected if The temp file is created in a world-writable directory without symlink protection
You are affected if XWine version 1.0.1 from Freshmeat is installed and the w_editeur component creates the 'temporaire' file in a predictable, writable location without O_EXCL or mkstemp() protection.
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 dataRemove any setuid/setgid bits from XWine if present, and implement secure temporary file handling using O_EXCL flag or mkstemp() to prevent symlink attacks. Restrict system access to untrusted local users.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0930 — 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-2008-0930 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