# CVE-2004-2714: Other in n/a

> Attackers can execute arbitrary code via format string vulnerabilities in Window Maker font specifications, affecting local users.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-2714, GHSA-f879-gmxv-6jv3

## What is CVE-2004-2714?

CVE-2004-2714 is a medium-severity vulnerability in n/a, published on 6 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in Window Maker 0.80.2 and earlier allows attackers to perform unknown actions via format string specifiers in a font specification in WMGLOBAL, probably a format string vulnerability.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2004-2714?

It affects 1 product.


Products: Windowmaker Windowmaker.

## How do I fix CVE-2004-2714?

Upgrade to a fixed version.

## Is CVE-2004-2714 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-1027](https://insights.sbomify.com/CVE-2001-1027/): Memory corruption in n/a (critical 10.0)
- [CVE-1999-1064](https://insights.sbomify.com/CVE-1999-1064/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-1277](https://insights.sbomify.com/CVE-2002-1277/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2714 and fix it if it is affected.

What it is: CVE-2004-2714 is a medium-severity vulnerability in n/a, published on 6 Oct 2007. 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-2004-2714 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-2004-2714/ (Markdown: https://insights.sbomify.com/CVE-2004-2714/index.md)
```

## Sources

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

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