Adobe · Acrobat and Reader · CWE-119 · published 2010-09-09
CVE-2010-2883Adobe Acrobat and Reader Stack-Based Buffer Overflow Vulnerability
This week Known exploited in the wild.
CVE-2010-2883 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2022-06-08. EPSS estimates an 81.4% chance of exploitation in the next 30 days, higher than 99% of all CVEs. This Acrobat and Reader vulnerability: CVSS 7.3 (v3.1), a successful attack gives total control of the component. CISA’s required action: Apply updates per vendor instructions. US federal agencies must remediate by 2022-06-22. Patch this week.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
CISA required action: Apply updates per vendor instructions. (federal due date 2022-06-22)
Patch events
Desktop appAdobe Acrobat and Reader
Stack-Based Buffer OverflowCVE-2010-2883
Why: Known exploited in the wild.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2022-06-08 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 81% (100th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.3 (v3.1)CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer
More from this vendor: all Adobe vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- Product
n/a(affected)
Description (from the CVE record)#
Stack-based buffer overflow in CoolType.dll in Adobe Reader and Acrobat 9.x before 9.4, and 8.x before 8.2.5 on Windows and Mac OS X, allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via a PDF document with a long field in a Smart INdependent Glyphlets (SING) table in a TTF font, as exploited in the wild in September 2010. NOTE: some of these details are obtained from third party information.
Quoted from the CVE Program record.