dbcve.org
DevscriptsApplication · Devscripts Devel Team

CVE-2013-6888

HIGH · 7.5 CVSS v2.0 Published 2014-01-07
Fix available
A fix is available. Upgrade to after 2.13.8 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Uscan in devscripts before 2.13.9 allows remote attackers to execute arbitrary code via a crafted tarball.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Uscan (a utility in devscripts package used for watching upstream software releases) before version 2.13.9 does not properly sanitize input from crafted tarballs, allowing remote attackers to inject and execute arbitrary code via the tarball filename or contents.

MitigationUpgrade devscripts to version 2.13.9 or later. Until then, avoid processing untrusted tarballs with uscan and consider network isolation for systems running this tool.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DevscriptsApplication
Affected:<= 2.13.8= 2.13.0= 2.13.1= 2.13.2= 2.13.3= 2.13.4= 2.13.5= 2.13.6= 2.13.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify devscripts package installation
    Run `dpkg -l devscripts` on Debian/Ubuntu systems or `rpm -q devscripts` on Red Hat/CentOS systems to check if the devscripts package is installed.
    Affected if The package is not installed or the query returns no package found.
  2. Check installed devscripts version
    Run `dpkg -s devscripts | grep Version` or `rpm -q --qf '%{VERSION}' devscripts` to retrieve the exact version number of the installed devscripts package.
    Affected if The displayed version is 2.13.8 or earlier (any version from 2.13.0 through 2.13.8).
  3. Locate the uscan binary
    Run `which uscan` or `command -v uscan` to confirm the uscan utility is present on the system.
    Affected if The uscan binary exists and the devscripts version is 2.13.8 or earlier.
  4. Check uscan usage context
    Review any configuration files in /etc/devscripts.conf or ~/.devscripts that may contain uscan-related settings, and check for cron jobs or scripts that invoke uscan.
    Affected if Uscan is configured to run automatically or is being used, especially with untrusted upstream tarball sources.

A system is affected if devscripts version 2.13.8 or earlier is installed and the uscan utility is present and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2.13.8
Interim mitigation

Upgrade devscripts to version 2.13.9 or later. Until then, avoid processing untrusted tarballs with uscan and consider network isolation for systems running this tool.

Fix this in Devscripts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-6888 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-6888 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data