# CVE-2007-6211: Privilege escalation in n/a

> Local users can gain privileges by appending to arbitrary files if the sing utility is configured with setuid permissions.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/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:** No
- **Published:** 4 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fjjj-5jfv-h4xq

## What is CVE-2007-6211?

CVE-2007-6211 is a high-severity vulnerability in n/a, published on 4 Dec 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Send ICMP Nasty Garbage (sing) on Debian GNU/Linux allows local users to append to arbitrary files and gain privileges via the -L (output log file) option.  NOTE: this issue is only a vulnerability in limited environments, since sing is not installed setuid, and the administrator would need to override a non-setuid default during installation.

Weakness: CWE-264

## Which versions are affected by CVE-2007-6211?

It affects 1 product.


Products: Sing Sing.

## How do I fix CVE-2007-6211?

No fix has been published for CVE-2007-6211 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-6211 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-6211 exists.

Public exploit code:

- Send ICMP Nasty Garbage (SING) - Append File Logrotate (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-6211 and fix it if it is affected.

What it is: CVE-2007-6211 is a high-severity vulnerability in n/a, published on 4 Dec 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-6211 exists.

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-2007-6211/ (Markdown: https://insights.sbomify.com/CVE-2007-6211/index.md)
```

## Sources

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

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