CVE-2024-9246
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFoxit PDF Reader Annotation Out-Of-Bounds Read Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Foxit PDF Reader. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of Annotation objects. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-24135.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFoxit PDF Reader contains an out-of-bounds read vulnerability in its Annotation object handling. The lack of proper validation of user-supplied data allows reading past the end of an allocated buffer, potentially exposing sensitive memory contents. While primarily an information disclosure flaw, it can be chained with other vulnerabilities to achieve code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 11.2.10.53951>= 12.0, <= 12.1.7.15526>= 13.0, <= 13.1.3.22478>= 2023.0, <= 2023.3.0.23028>= 2024.0, <= 2024.2.3.25184<= 2024.2.3.25184CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Foxit PDF Reader versionOpen Foxit PDF Reader, then go to Help > About Foxit Reader. Alternatively, right-click the application in the file explorer, select Properties, and check the File version on the Details tab.Affected if The displayed version falls within <= 2024.2.3.25184 for Foxit PDF Reader
-
Verify annotation feature is in useThe vulnerability exists in the Annotation object handling component. Check if the application has ever opened PDF files containing annotations (comments, highlights, stamps, or other markup). This is logged in recent file history or can be tested by opening a PDF with annotations.Affected if PDF files with annotations have been opened or the annotation feature is active in the reader
-
Confirm version matches all affected rangesCross-reference the installed version against all known affected ranges: 11.2.10.53951 and below; 12.0 through 12.1.7.15526; 13.0 through 13.1.3.22478; 2023.0 through 2023.3.0.23028; 2024.0 through 2024.2.3.25184. Use decimal comparison for each version segment.Affected if Installed version matches any of the affected ranges listed above
A user is affected if they have Foxit PDF Reader version 2024.2.3.25184 or lower and open PDF files containing specially crafted annotation objects.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the vendor-supplied patch or update Foxit PDF Reader to the latest version. Until patched, avoid opening untrusted PDF files or visiting suspicious websites.
Foxit PDF Reader version > 2024.2.3.25184; Foxit PDF Editor version > 11.2.10.53951, > 12.1.7.15526, > 13.1.3.22478, > 2023.3.0.23028
- 1. Open Foxit PDF Reader or PDF Editor application
- 2. Navigate to Help > Check for Updates or About (depending on product version)
- 3. Download and install the latest version from the official Foxit website at www.foxit.com
- 4. Alternatively, download directly from https://www.foxit.com/downloads/
- 5. Restart the application after installation
- 6. Verify the installed version is newer than the vulnerable versions listed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9246 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-9246 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data