Advanced Package ToolApplication · Debian
CVE-2009-1358
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 · uneditedapt-get in apt before 0.7.21 does not check for the correct error code from gpgv, which causes apt to treat a repository as valid even when it has been signed with a key that has been revoked or expired, which might allow remote attackers to trick apt into installing malicious repositories.
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 · high confidenceapt-get in apt versions before 0.7.21 fails to properly validate the error codes returned by gpgv when verifying repository signatures. Specifically, apt does not check for error codes indicating that a signing key has been revoked or expired, causing apt to treat repositories as valid even when signed with compromised keys. This allows remote attackers to inject malicious packages by compromising a signing key and having apt trust the malicious repository.
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
Advanced Package ToolApplication
<= 0.7.20= 0.7.0= 0.7.1= 0.7.2= 0.7.2-0.1= 0.7.10= 0.7.11= 0.7.12= 0.7.13= 0.7.14= 0.7.15= 0.7.16
AptApplication
= 0.0.1= 0.0.2= 0.0.3= 0.0.4= 0.0.5= 0.0.6= 0.0.7= 0.0.8= 0.0.9= 0.0.10= 0.0.11= 0.0.12CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed apt versionRun dpkg -l | grep '^ii.*apt ' or apt-get --version to retrieve the installed apt package version numberAffected if The installed version is 0.7.20 or earlier, or matches one of these specific versions: 0.7.0, 0.7.1, 0.7.2, 0.7.2-0.1, 0.7.10, 0.7.11, 0.7.12, 0.7.13, 0.7.14, 0.7.15, 0.7.16, or any version 0.0.1 through 0.0.12
If the installed apt version is 0.7.20 or earlier, or matches any of the specifically listed affected versions, the system is vulnerable to CVE-2009-1358
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade apt to version 0.7.21 or later, which correctly validates gpgv error codes and rejects signatures from revoked or expired keys.
apt version 0.7.21 or later
- 1. Update your package lists: sudo apt-get update
- 2. Upgrade the apt package: sudo apt-get install apt
- 3. Verify the installed version is 0.7.21 or later: apt-get --version
- 4. For systems where the fixed version is not available in repositories, consider upgrading the entire distribution or obtaining apt 0.7.21 from trusted source archives
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Advanced Package Tool
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-1358 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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