CVE-2014-4646
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 · uneditedBuffer overflow in the FPDFBookmark_GetTitle method in Foxit PDF SDK DLL before 3.1.1.5005 allows context-dependent attackers to execute arbitrary code via unspecified vectors.
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 · moderate confidenceBuffer overflow vulnerability in the FPDFBookmark_GetTitle method of Foxit PDF SDK DLL allows arbitrary code execution via unspecified vectors, likely through malformed bookmark title data in PDF files.
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<= 3.1.1.2927CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 the Foxit PDF SDK DLL fileSearch the system for DLL files named fpdfsdk.dll or similar Foxit PDF SDK library files. Common paths include application directories or system folders where third-party PDF libraries are stored.Affected if The DLL file cannot be found (SDK not in use) or is found but version cannot be determined.
-
Extract the DLL version informationRight-click the DLL file, select Properties, then navigate to the Details tab to view the File Version. Alternatively, use a tool like sigcheck or PowerShell's Get-ItemProperty to read the version info from the file metadata.Affected if The DLL version cannot be determined or is not visible in the file properties.
-
Compare installed version against affected rangeCompare the extracted version number to the affected range. The vulnerability affects versions 3.1.1.2927 and earlier. Versions 3.1.1.5005 and later contain the fix.Affected if The installed version is 3.1.1.2927 or lower, indicating the vulnerable DLL is in use.
-
Verify the application uses FPDFBookmark_GetTitle functionalityDetermine if any applications or services in the environment use the Foxit PDF SDK to process PDF files. This method is called when reading or parsing bookmark data (Outline entries) from PDF documents.Affected if The environment processes PDF files using Foxit PDF SDK and the SDK version is within the affected range.
The environment is affected if the Foxit PDF SDK DLL in use has version 3.1.1.2927 or lower and the SDK is used to process PDF files containing bookmark data.
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.
From vendor dataUpgrade Foxit PDF SDK to version 3.1.1.5005 or later to obtain the patched DLL that addresses the buffer overflow in FPDFBookmark_GetTitle.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4646 — 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-2014-4646 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