CVE-2009-2982 json
An unspecified certificate in Adobe Reader and Acrobat 9.x before 9.2, 8.x before 8.1.7, and possibly 7.x through 7.1.4 might allow remote…
published 2009-10-19 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-2967
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
An unspecified certificate in Adobe Reader and Acrobat 9.x before 9.2, 8.x before 8.1.7, and possibly 7.x through 7.1.4 might allow remote attackers to conduct a "social engineering attack" via unknown vectors.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2009-2982 updated cvss 4.3
acroread: certificate compromise (social engineering attack) fixed in 8.1.7 (APSB09-15)
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.73% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
us-cert.gov
/cas/techalerts/TA09-286B.html
third-party-advisory, patch, us-government-resource
-
adobe.com
/support/security/bulletins/apsb09-15.html
patch, vendor-advisory
-
vupen.com
/english/advisories/2009/2898
vdb-entry, patch, vendor-advisory
-
securityfocus.com
/bid/36638
vdb-entry
-
securitytracker.com
/id?1023007
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6365
vdb-entry, signature
Sources
- CVE List CVE-2009-2982
- NVD CVE-2009-2982
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.