CVE-2013-6888 json
Uscan in devscripts before 2.13.9 allows remote attackers to execute arbitrary code via a crafted tarball.
published 12y ago modified 4mo ago also EUVD-2013-6690
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.1%
- EPSS 4.1% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
Uscan in devscripts before 2.13.9 allows remote attackers to execute arbitrary code via a crafted tarball.
Patch / fix
- devscripts Debian 14, Debian 13, Debian 12 2.13.9
debian advisories DEBIAN-CVE-2013-6888
Is CVE-2013-6888 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-6888 updated cvss 6.8
devscripts: arbitrary code execution in uscan
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
4.09% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
References
-
ubuntu.com
/usn/USN-2084-1
vendor-advisory
-
debian.org
/security/2014/dsa-2836
vendor-advisory
-
securityfocus.com
/bid/64656
vdb-entry
-
marc.info
/?l=oss-security&m=138900586911271&w=2
mailing-list
-
secunia.com
/advisories/56579
third-party-advisory
-
secunia.com
/advisories/56192
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/90107
vdb-entry
- anonscm.debian.org /gitweb/?p=collab-maint/devscripts.git%3Ba=commitdiff%3Bh=02c6850d973e3e1246fde72edab27f03d63acc52
Sources
- CVE List CVE-2013-6888
- NVD CVE-2013-6888
Fencer Intel 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.