CVE-2013-7085
Summary
| CVE | CVE-2013-7085 |
|---|---|
| State | PUBLISHED |
| Assigner | mitre |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2013-12-14 17:21:47 UTC |
| Updated | 2026-04-29 01:13:23 UTC |
| Description | Uscan in devscripts 2.13.5, when USCAN_EXCLUSION is enabled, allows remote attackers to delete arbitrary files via a whitespace character in a filename. |
Risk And Classification
Primary CVSS: v2.0 5.8 from [email protected]
AV:N/AC:M/Au:N/C:P/I:N/A:P
EPSS: 0.009950000 probability, percentile 0.770680000 (date 2026-05-12)
Problem Types: CWE-20 | n/a
CVSS v2.0 Breakdown
Access Vector
NetworkAccess Complexity
MediumAuthentication
NoneConfidentiality
PartialIntegrity
NoneAvailability
PartialAV:N/AC:M/Au:N/C:P/I:N/A:P
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Devscripts Devel Team | Devscripts | 2.13.5 | All | All | All |
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Debian devscripts 'uscan' Filename Handling Arbitrary File Deletion Vulnerability | af854a3a-2127-422b-91ae-364da2661108 | www.securityfocus.com | |
| IBM X-Force Exchange | af854a3a-2127-422b-91ae-364da2661108 | exchange.xforce.ibmcloud.com | |
| #732006 - uscan: broken handling of filenames with whitespace (CVE-2013-7085) - Debian Bug report logs | af854a3a-2127-422b-91ae-364da2661108 | bugs.debian.org | Exploit |
| osvdb.org/100917 | af854a3a-2127-422b-91ae-364da2661108 | osvdb.org | |
| oss-security - CVE Request: devscripts (uscan) broken handling of filenames with whitespace | af854a3a-2127-422b-91ae-364da2661108 | www.openwall.com | |
| oss-security - Re: CVE Request: devscripts (uscan) broken handling of filenames with whitespace | af854a3a-2127-422b-91ae-364da2661108 | www.openwall.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.