CVE-2019-8048
published 2019-08-20CVE-2019-8048: Adobe Acrobat and Reader versions 2019.012.20035 and earlier, 2019.012.20035 and earlier, 2017.011.30142 and earlier, 2017.011.30143 and earlier…
PriorityP269critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EXPLOIT
EPSS
35.37%
98.3th percentile
Adobe Acrobat and Reader versions 2019.012.20035 and earlier, 2019.012.20035 and earlier, 2017.011.30142 and earlier, 2017.011.30143 and earlier, 2015.006.30497 and earlier, and 2015.006.30498 and earlier have a buffer error vulnerability. Successful exploitation could lead to arbitrary code execution .
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| adobe | acrobat_dc | >= 15.006.30060 < 15.006.30499 | 15.006.30499 |
| adobe | acrobat_dc | >= 15.008.20082 < 19.012.20036 | 19.012.20036 |
| adobe | acrobat_dc | >= 17.011.30059 < 17.011.30144 | 17.011.30144 |
| adobe | acrobat_reader_dc | >= 15.006.30060 < 15.006.30499 | 15.006.30499 |
| adobe | acrobat_reader_dc | >= 15.008.20082 < 19.012.20036 | 19.012.20036 |
| adobe | acrobat_reader_dc | >= 17.011.30059 < 17.011.30144 | 17.011.30144 |
| adobe | adobe_acrobat_and_reader | — | — |
Detection & IOCsextracted from sources · hover to see the quote
bytes↗
0xFF 0x7F at offset 0x123bff in CFF font stream (mutated from 0xC0 0x95)
- →Crash/exploitation occurs in CoolType!CTCleanup+0x22e92 via an out-of-bounds write (mov dword ptr [esi+ecx*4],eax) when parsing a malformed CFF font stream inside a PDF. Monitor for access violations originating from CoolType.dll during PDF rendering. ↗
- →The vulnerability is triggered immediately upon opening a specially crafted PDF containing a malformed CFF font stream. The two-byte mutation (0xC0 0x95 → 0xFF 0x7F) at offset 0x123bff in the font stream is the trigger. Inspect PDF files for anomalous CFF font stream values at that offset. ↗
- →The call stack involves AGM.dll (AGMInitialize) calling into CoolType.dll font parsing routines. Suspicious call chains from AGM!AGMInitialize into CoolType!CTInit/CTCleanup during PDF open events should be flagged. ↗
- →Reproduces on Adobe Acrobat Reader DC version 2019.012.20035 on Windows 10. Prioritize detection/patching on this specific version. ↗
- ·Affected versions span multiple Adobe Acrobat/Reader tracks; all listed versions are vulnerable and require patching. ↗
- ·The crash reproduces both with and without PageHeap enabled, meaning standard heap instrumentation alone is insufficient to prevent exploitation. ↗
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.07.5HIGHAV:N/AC:L/Au:N/C:P/I:P/A:P
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-v4j4-6q7q-jhmq: Adobe Acrobat and Reader versions, 2019
ghsa_unreviewed·2022-05-24
CVE-2019-8048 [CRITICAL] CWE-119 GHSA-v4j4-6q7q-jhmq: Adobe Acrobat and Reader versions, 2019
Adobe Acrobat and Reader versions, 2019.012.20035 and earlier, 2019.012.20035 and earlier, 2017.011.30142 and earlier, 2017.011.30143 and earlier, 2017.011.30142 and earlier, 2015.006.30497 and earlier, and 2015.006.30498 and earlier have a buffer error vulnerability. Successful exploitation could lead to arbitrary code execution.
Project0
Part II: Returning to Adobe Reader symbols on macOS - Project Zero
project_zero·2020-01-01
CVE-2019-8042 Part II: Returning to Adobe Reader symbols on macOS - Project Zero
Posted by Mateusz Jurczyk, Project Zero
In a blog post titled "The story of Adobe Reader symbols" published in October 2019, I presented an analysis of the debug symbols shipped with some older versions of Adobe Reader for Unix-family systems released between 1997-2013. Such symbols can prove immensely useful for both understanding the inner workings of various Reader components while reverse engineering, and for automated tasks such as crash classification and deduplication in fuzzing projects. In that blog post, I only briefly mentioned the macOS Reader packages as containing up-to-date symbols for the JP2K and 3D components, but missing any other interesting information beyond that. Upon a closer and more thorough inspection of the Mac releases, I have discovered that in fact more deb
No detection rules found.
No writeups or analysis indexed.
2019-08-20
Published