Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-7382

The PdfFontFactory.cpp:200:88 code in PoDoFo 0.9.5 allows remote attac ...

Overview

Published
3 Apr 2017
Modified
17 Jun 2026
Medium CVE
0 Registry packages
7 OS packages
4 Linux distributions
Yes Fix available

Description

The PdfFontFactory.cpp:200:88 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.

Source: OX vulnerability database

Severity

5.5 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Local
Attack complexity
Low
Privileges required
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

Weakness: CWE-476

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 11 fixes

alpine 4 releases · 1 package

fixed 4
podofo
alpine fixes for CVE-2017-7382
ReleasePackageFixed in
3.22 podofo 0.9.6-r0
3.23 podofo 0.9.6-r0
3.24 podofo 0.9.6-r0
edge podofo 0.9.6-r0

debian 4 releases · 1 package

fixed 4
libpodofo
debian fixes for CVE-2017-7382
ReleasePackageFixed in
11 libpodofo 0.9.4-6
12 libpodofo 0.9.4-6
13 libpodofo 0.9.4-6
14 libpodofo 0.9.4-6

echo 1 release · 1 package

fixed 1
libpodofo
echo fixes for CVE-2017-7382
ReleasePackageFixed in
libpodofo 0.9.4-6

openSUSE 1 release · 2 packages

fixed 2
libpodofo-0-10-devel libpodofo-devel
openSUSE fixes for CVE-2017-7382
ReleasePackageFixed inAdvisory
Tumbleweed libpodofo-0-10-devel +2 0.10.5-1.1 openSUSE-SU-2025:15521-1
Tumbleweed libpodofo-devel +2 0.9.7-2.2 openSUSE-SU-2024:11178-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.