dbcve.org
DevscriptsApplication · Debian

CVE-2013-7325

HIGH · 8.8 CVSS v3.1 Published 2019-12-03
Fix available
A fix is available. Upgrade to 2.13.19 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
An issue exists in uscan in devscripts before 2.13.19, which could let a remote malicious user 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

The uscan tool in devscripts before version 2.13.19 contains a vulnerability allowing remote attackers to execute arbitrary code by providing a crafted tarball. The vulnerability likely stems from insufficient validation of archive contents during extraction or processing, enabling path traversal or command injection.

MitigationUpdate devscripts to version 2.13.19 or later. Until patched, avoid using uscan on tarballs from untrusted sources.

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.19
Debian LinuxOperating system
Affected:= 7.0= 8.0= 9.0= 10.0= 11.0

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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 is installed
    Run: dpkg -l | grep devscripts or apt list --installed 2>/dev/null | grep devscripts
    Affected if The devscripts package is not installed on the system
  2. Check installed devscripts version
    Run: dpkg -l devscripts | grep devscripts or dpkg -s devscripts | grep Version
    Affected if The installed version is lower than 2.13.19 (e.g., 2.13.18, 2.12.x, etc.)
  3. Confirm uscan binary exists
    Run: which uscan or ls -la /usr/bin/uscan
    Affected if The uscan binary exists and is executable at /usr/bin/uscan or similar path
  4. Verify Debian OS version
    Run: cat /etc/debian_version
    Affected if The system runs Debian 7.0, 8.0, 9.0, 10.0, or 11.0 with devscripts versions below 2.13.19
  5. Check if uscan has been used recently
    Review shell history or check for recent uscan invocations in logs under /var/log or user home directories
    Affected if uscan has been executed on tarballs from untrusted sources

A system is affected if devscripts version is below 2.13.19 and the uscan tool is installed 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 2.13.19 or later
Fixed in 2.13.19
Interim mitigation

Update devscripts to version 2.13.19 or later. Until patched, avoid using uscan on tarballs from untrusted sources.

Fix this in Devscripts Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-7325 — 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-7325 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