CVE-2007-6211 json
Send ICMP Nasty Garbage (sing) on Debian GNU/Linux allows local users to append to arbitrary files and gain privileges via the -L (output l…
published 2007-12-04 18 y ago modified 2026-06-16 4 mo ago also EUVD-2007-6179
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 1
- Exploit-DB
Summary
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.
Timeline
- Published
- First public exploit (EDB-4698)
Exploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-4698 Send ICMP Nasty Garbage (SING) - Append File Logrotate local, 2007-12-06
- securityreason.com http://securityreason.com/securityalert/3412 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/26679 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
securityreason.com
/securityalert/3412
third-party-advisory, exploit
-
securityfocus.com
/bid/26679
vdb-entry, exploit
-
osvdb.org
/44157
vdb-entry
-
securityfocus.com
/archive/1/484591/100/200/threaded
mailing-list
-
securityfocus.com
/archive/1/484472/100/0/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/38822
vdb-entry
Sources
- CVE List CVE-2007-6211
- NVD CVE-2007-6211
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.