CVE-2024-9255
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 Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code 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 validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-25174.
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 confidenceA Use-After-Free vulnerability exists in Foxit PDF Reader's Annotation object handling. The application fails to validate object existence before performing operations on annotation objects, allowing an attacker to manipulate memory after an object has been freed. This enables arbitrary code execution in the context of the current user process when a victim opens a malicious PDF or visits a crafted webpage.
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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Check installed Foxit PDF Reader versionOpen Foxit PDF Reader, then navigate to Help > About Foxit Reader (or press Ctrl+Alt+F5). The version number displays in the dialog box that appears.Affected if The displayed version is 2024.2.3.25184 or earlier (any version listed in the affected ranges).
-
Verify version via Windows Programs and FeaturesOpen Windows Control Panel > Programs and Features (or Settings > Apps > Installed apps). Locate 'Foxit PDF Reader' in the list and note the version shown in the Version column.Affected if The version shown is 2024.2.3.25184 or earlier.
-
Check Foxit Editor version if installedIf using Foxit PDF Editor instead of Reader, open the application and go to Help > About Foxit PDF Editor. Note the version displayed.Affected if The version falls within any of the affected ranges: <= 11.2.10.53951, >= 12.0 and <= 12.1.7.15526, >= 13.0 and <= 13.1.3.22478, >= 2023.0 and <= 2023.3.0.23028, or >= 2024.0 and <= 2024.2.3.25184.
A user is affected if Foxit PDF Reader version is 2024.2.3.25184 or earlier, or Foxit PDF Editor version falls within any of the listed affected ranges.
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 · scopedUpdate Foxit PDF Reader to the latest version containing the security patch. Until then, exercise caution with PDF files from untrusted sources and consider disabling the PDF browser plugin to prevent drive-by attacks.
Pdf Reader: 2024.2.4 or later; Pdf Editor: 11.2.11 or later, 12.1.8 or later, 13.1.4 or later, 2023.3.1 or later (or migrate to latest 2024 release)
- Navigate to the official Foxit website at www.foxit.com and locate the Downloads or Support section
- Identify your current product (Pdf Reader or Pdf Editor) and version number
- Download the latest version of Foxit Pdf Reader or Pdf Editor from the official Foxit website
- Close any running instances of Foxit PDF applications
- Install the downloaded update by following the installation wizard prompts
- Restart your computer if prompted by the installer
- Verify the installed version by opening Foxit and checking Help > About Foxit Reader/Editor
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9255 — 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-9255 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