Adobe Reader DC patched 3D PDF memory corruption flaws in U3D texture handling
Adobe patched two memory corruption vulnerabilities in Adobe Reader DC 2019.010.20064 affecting the rendering of 3D content embedded in PDF files. Tracked as CVE-2019-7119 and CVE-2019-7120, the flaws were found in the 2d.x3d and related rt3d processing path used for ECMA-363 Universal 3D (U3D) resources and external texture images. One bug allowed an arbitrary out-of-bounds write in TRGB::Read() and was observed crashing through 2d!png_set_filter_heuristics, while the other involved an out-of-bounds condition in TIF::Read() tied to _LoadILBM(), reported as an out-of-bounds read at crash time but patched by Adobe as an out-of-bounds write.
The vulnerabilities could be triggered with a crafted U3D file that manipulated texture metadata and referenced external image files, including .iff content, causing memory corruption when a user enabled 3D content display in a PDF. The exposure was not present in a default configuration unless 3D PDF rendering was enabled, but organizations that regularly exchange CAD and other 3D documents faced higher risk. Adobe addressed both issues in advisory APSB19-17 after coordinated disclosure from STAR Labs.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
3 events from the most recent confirmed update back to the earliest known activity.
Adobe releases APSB19-17 patch for CVE-2019-7119 and CVE-2019-7120
Adobe patched the two Adobe Reader DC vulnerabilities through advisory APSB19-17. The fixes addressed memory corruption issues in the 2d.x3d/rt3d processing path related to external texture image parsing in embedded 3D PDF content.
Adobe patches CVE-2019-7035 in APSB19-07
Adobe acknowledged and fixed CVE-2019-7035, an Adobe Reader DC 3D PDF parsing flaw involving external GIF texture handling in the 2d.x3d module. STAR Labs' advisory says the bug could cause an arbitrary one-byte XOR write in the sandboxed process when 3D content display was enabled.
STAR Labs reports Adobe Reader DC 3D parsing flaws to Adobe
STAR Labs notified Adobe of two vulnerabilities in Adobe Reader DC's 3D content handling path, later assigned CVE-2019-7119 and CVE-2019-7120. Both issues involved crafted U3D/external texture image processing and could lead to memory corruption when 3D PDF content was enabled.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
8 references tracked. Mallory keeps watching after this page renders.
(CVE-2019-7142) Acrobat Reader DC 2d.x3d!_LoadRGB() Out-of-Bounds Read/Write in TRGB::expandrow() | STAR Labs
starlabs.sg
Open source(CVE-2019-7119) Acrobat Reader DC 2d.x3d!_LoadRGB() Out-of-Bounds Write in TRGB::Read() | STAR Labs
starlabs.sg
Open source(CVE-2019-7122) Acrobat Reader DC 2d.x3d!_LoadTIFF() Out-of-Bounds Read in TTIFFread::TifReadChunkyRGB() | STAR Labs
starlabs.sg
Open source(CVE-2019-7121) Acrobat Reader DC 2d.x3d!_LoadILBM() Out-of-Bounds Read in TIF::Read() | STAR Labs
starlabs.sg
Open source(CVE-2019-7118) Acrobat Reader DC 2d.x3d!_LoadRGB() Out-of-Bounds Write in TRGB::Read() | STAR Labs
starlabs.sg
Open source(CVE-2019-7123) Acrobat Reader DC 2d.x3d!_LoadRGB() Memory Corruption in TRGB::expandrow() | STAR Labs
starlabs.sg
Open source(CVE-2019-7120) Acrobat Reader DC 2d.x3d!_LoadILBM() Out-of-Bounds Read in TIF::Read() | STAR Labs
starlabs.sg
Open source(CVE-2019-7035) Acrobat Reader DC 2d.x3d!_LoadGIF() Arbitrary Write in TGIF::PutPixel() | STAR Labs
starlabs.sg
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


