# CVE-2008-1687: Other in n/a

> Attackers can trigger macro expansion in GNU m4 due to unquoted output, potentially leading to incorrect filename usage.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-1687, ECHO-8f1c-8d22-666a, GHSA-r86c-jfhj-2f8j, ROOT-OS-DEBIAN-12-CVE-2008-1687

## What is CVE-2008-1687?

CVE-2008-1687 is a high-severity vulnerability in n/a, published on 9 Apr 2008. 

### Official description

The (1) maketemp and (2) mkstemp builtin functions in GNU m4 before 1.4.11 do not quote their output when a file is created, which might allow context-dependent attackers to trigger a macro expansion, leading to unspecified use of an incorrect filename.

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

It affects 1 product.


Products: Gnu M4.

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

Upgrade to a fixed version.

## Is CVE-2008-1687 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-1688](https://insights.sbomify.com/CVE-2008-1688/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-1687 is a high-severity vulnerability in n/a, published on 9 Apr 2008. 
Exploitation: There is no known exploitation of CVE-2008-1687 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-1687/ (Markdown: https://insights.sbomify.com/CVE-2008-1687/index.md)
```

## Sources

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

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