CVE-2017-7380
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 · uneditedThe doc/PdfPage.cpp:614:20 code in PoDoFo 0.9.5 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted PDF document.
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 confidencePoDoFo 0.9.5 contains a NULL pointer dereference vulnerability in doc/PdfPage.cpp at line 614 when processing PDF documents. When a crafted PDF document is parsed, the code attempts to dereference a NULL pointer, causing the application to crash and resulting in denial of service.
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= 0.9.5CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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 if PoDoFo is installedCheck for the presence of the PoDoFo library on the system. Common locations include /usr/lib/libpodofo.so, /usr/local/lib/libpodofo.so, or search using 'find / -name "libpodofo*" 2>/dev/null' or check installed packages via package manager (dpkg -l | grep podofo, rpm -qa | grep podofo)Affected if PoDoFo library is present on the system
-
Determine the installed PoDoFo versionIf a shared library is found, run 'podofo-config --version' or check the library version with 'strings libpodofo.so | grep -i "0\.9\.5"' or inspect binary metadata. Check any version files or headers installed with the libraryAffected if The version is exactly 0.9.5
-
Locate the vulnerable source fileSearch for doc/PdfPage.cpp in the PoDoFo source directory or installed headers: 'find / -path "*/doc/PdfPage.cpp" 2>/dev/null' or check in /usr/include/podofo/doc/PdfPage.cpp if headers are installedAffected if The file doc/PdfPage.cpp exists and contains the code at line 614 that performs pointer dereferencing without NULL checks
-
Assess PDF processing usageIdentify applications or services that use the PoDoFo library for PDF processing. Check application dependencies with 'ldd <application_binary>' or review application configuration for PDF handling modulesAffected if Any application or service on the system uses PoDoFo to process incoming or user-submitted PDF documents
A system is affected if PoDoFo version 0.9.5 is installed and any application uses it to process PDF documents, as the NULL pointer dereference in doc/PdfPage.cpp line 614 will cause a crash when parsing crafted PDFs.
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 dataApply the vendor patch or update to a patched version of PoDoFo. Implement input validation and NULL pointer checks in PdfPage.cpp:614 before dereferencing pointers to prevent crashes from malformed PDF input.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7380 — 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-2017-7380 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