# CVE-2008-0931: Misconfiguration in n/a

> Local attackers can modify insecurely permissioned Wine config files to execute arbitrary commands or cause denial of service.

- **Severity:** Medium 6.3 (`AV:L/AC:M/Au:N/C:N/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r6gx-g2r9-8q8m

## What is CVE-2008-0931?

CVE-2008-0931 is a medium-severity vulnerability in n/a, published on 4 Mar 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

w_export.c in XWine 1.0.1 on Debian GNU/Linux sets insecure permissions (0666) for /etc/wine/config, which might allow local users to execute arbitrary commands or cause a denial of service by modifying the file.

Weakness: CWE-264

## Which versions are affected by CVE-2008-0931?

It affects 1 product.


Products: Xwine Xwine.

## How do I fix CVE-2008-0931?

Apply the vendor's patch.

## Is CVE-2008-0931 being exploited?

There is no known exploitation of CVE-2008-0931 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0931 and fix it if it is affected.

What it is: CVE-2008-0931 is a medium-severity vulnerability in n/a, published on 4 Mar 2008. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-0931 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2008-0931/ (Markdown: https://insights.sbomify.com/CVE-2008-0931/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-0931
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-0931
- OSV: https://osv.dev/vulnerability/CVE-2008-0931

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-0931/
Summaries are generated and may contain mistakes; the official description above is the record.