CVE-2021-21017 is a heap-based buffer overflow vulnerability affecting Adobe Acrobat Reader DC and related supported release lines, including versions 2020.013.20074 and earlier, 2020.001.30018 and earlier, and 2017.011.30188 and earlier. The flaw can be triggered when the application processes a malicious file, causing memory corruption in heap-allocated data structures. A successful exploit can lead to arbitrary code execution in the security context of the current user. The vulnerability was reported as being actively exploited in the wild, with observed exploitation affecting Windows systems, and it also affects Adobe Reader on Windows and macOS.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit for CVE-2021-21017, a heap overflow vulnerability in Adobe Acrobat Reader (notably version 2020.013.20074, IA32 plugin). The repository contains three files: a JavaScript file (CVE-2021-21017.js) with the exploit logic, a malicious PDF (CVE-2021-21017.pdf) embedding the JavaScript, and a README.md explaining the vulnerability and exploitation technique. The exploit leverages a type confusion in the handling of the PDF's baseURL (when encoded as UTF-16BE), which, when combined with a crafted relative URL and the submitForm API, leads to an out-of-bounds read and heap overflow. The JavaScript performs heap spraying to increase reliability. The attack vector is a malicious PDF file, and the main fingerprintable endpoint is the PDF's BaseURL entry in UTF-16BE. The exploit is a PoC and primarily causes a crash or memory corruption, with no weaponized payload.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.