CVE-2009-0837
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 · uneditedStack-based buffer overflow in Foxit Reader 3.0 before Build 1506, including 1120 and 1301, allows remote attackers to execute arbitrary code via a long (1) relative path or (2) absolute path in the filename argument in an action, as demonstrated by the "Open/Execute a file" action.
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 confidenceStack-based buffer overflow in Foxit Reader 3.0 before Build 1506 allows remote code execution via a specially crafted PDF file containing a long filename path in the 'Open/Execute a file' action. The vulnerability occurs when the application processes an overly long relative or absolute path, overflowing a stack-allocated buffer and enabling arbitrary 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 dataall versionsCVSS 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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Locate Foxit Reader installationSearch for Foxit Reader executable (foxitreader.exe) in common installation directories such as C:\Program Files\Foxit Software\Foxit Reader\ or check Program Files (x86) for 32-bit installations. Use file explorer or command: dir /s C:\*foxitreader.exeAffected if Foxit Reader executable is found on the system
-
Determine installed version numberRight-click the Foxit Reader executable, select Properties, then view the Details tab for version information. Alternatively, right-click the application in Start menu, select Properties, and check the version field.Affected if Version information is displayed showing Build number or full version string
-
Compare against affected version rangeCompare the discovered version/build number to the affected range: Foxit Reader 3.0 all versions before Build 1506. Look specifically for the Build number in the version string (for example: 3.0.1505 or earlier indicates vulnerability).Affected if The installed version is Foxit Reader 3.0 with Build number lower than 1506, or the version string indicates a pre-patch release of 3.0
A system is affected if Foxit Reader 3.0 is installed with a Build number earlier than 1506, as only versions from Build 1506 onward contain the fix for this buffer overflow.
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 · scopedUpgrade Foxit Reader to version 3.0 Build 1506 or later. Until patched, avoid opening untrusted PDF files from unknown or untrusted sources.
Foxit Reader 3.0 Build 1506 or later
- 1. Open Foxit Reader application
- 2. Navigate to Help menu
- 3. Select 'Check for Updates' or 'About Foxit Reader' to verify current build version
- 4. If current version is before Build 1506, download the latest Foxit Reader version from the official website at https://www.foxitsoftware.com/downloads/
- 5. Run the installer and follow the prompts to complete the upgrade
- 6. After installation, verify the build number is 1506 or later via Help > About Foxit Reader
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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 $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0837 — 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-2009-0837 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