CVE-2008-1530
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 · uneditedGnuPG (gpg) 1.4.8 and 2.0.8 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via crafted duplicate keys that are imported from key servers, which triggers "memory corruption around deduplication of user IDs."
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 confidenceGnuPG 1.4.8 and 2.0.8 contain a memory corruption vulnerability during the import of crafted duplicate keys from key servers. The deduplication process for user IDs triggers memory corruption that can be exploited for arbitrary code execution or denial of service.
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= 1.4.8= 2.0.8CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 GnuPG versionRun 'gpg --version' and examine the version number in the outputAffected if The version displayed is exactly 1.4.8 or 2.0.8
-
Confirm keyserver configuration existsInspect the GnuPG configuration file (typically ~/.gnupg/gpg.conf or /etc/gnupg/gpg.conf) for any 'keyserver' directive linesAffected if A keyserver directive is present in the configuration
-
Identify recent key import operations from key serversReview command history or logs for usage of 'gpg --recv-keys', 'gpg --search-keys', or 'gpg --keyserver' commandsAffected if Keys have been imported from a key server using the installed GnuPG version
You are affected if your installed GnuPG version is exactly 1.4.8 or 2.0.8 AND you have imported keys from a key server, as the vulnerability is triggered during the deduplication of crafted duplicate user IDs during key import.
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 GnuPG to a patched version beyond 1.4.8 and 2.0.8, and avoid importing keys from untrusted or unknown key servers until the upgrade is complete.
GnuPG 1.4.9+ or 2.0.9+ (later stable releases preferred)
- 1. Identify which GnuPG version is currently installed by running 'gpg --version'
- 2. For GnuPG 1.4.x users: Upgrade to GnuPG 1.4.9 or later from https://www.gnupg.org/download/
- 3. For GnuPG 2.0.x users: Upgrade to GnuPG 2.0.9 or later from https://www.gnupg.org/download/
- 4. Verify the new version is installed: 'gpg --version'
- 5. Test that key import from servers still works correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-1530 — 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-2008-1530 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