CVE-2017-13722: In the pcfGetProperties function in bitmap/pcfread.c in libXfont through 1.5.2 and 2.x before 2.0.2, a missing boundary check (for PCF files…
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: libxfont (Debian:12) 1:2.0.1-4; libxfont (Debian:7) 1:1.4.5-5+deb7u1; libxfont (Debian:8) 1:1.5.1-1+deb8u1.
Low priority for now. Upgrade to libxfont (Debian:12) 1:2.0.1-4; libxfont (Debian:7) 1:1.4.5-5+deb7u1; libxfont (Debian:8) 1:1.5.1-1+deb8u1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the pcfGetProperties function in bitmap/pcfread.c in libXfont through 1.5.2 and 2.x before 2.0.2, a missing boundary check (for PCF files) could be used by local attackers authenticated to an Xserver for a buffer over-read, for information disclosure or a crash of the X server.
- Published
- Oct 11, 2017
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 34th percentile
- CWE
- CWE-125
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| x.org | libxfont | cpe:2.3:a:x.org:libxfont |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- x.org libxfontup to 1.5.2 inclusive
- x.org libxfont2.0.0
- x.org libxfont2.0.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libxfont | before 1:2.0.1-4 | 1:2.0.1-4 |
| Debian:7 | libxfont | before 1:1.4.5-5+deb7u1 | 1:1.4.5-5+deb7u1 |
| Debian:8 | libxfont | before 1:1.5.1-1+deb8u1 | 1:1.5.1-1+deb8u1 |
| Debian:9 | libxfont | before 1:2.0.1-3+deb9u1 | 1:2.0.1-3+deb9u1 |
| openSUSE:Tumbleweed | libXfont | before 1.5.4-2.18 | 1.5.4-2.18 |
| SUSE:Linux Enterprise Desktop 12 SP2 | libXfont | before 1.5.1-11.3.12 | 1.5.1-11.3.12 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | xorg-x11-libs | before 7.4-8.26.50.5.3 | 7.4-8.26.50.5.3 |
Same product
x.org: all recordsOther highest-scoring records for the same primary product.
- CVE-2007-1351Integer overflow in the bdfReadCharacters function in bdfread.c in (1) X.Org libXfont before 20070403 and (2) freetype 2.3.2 and earlier…36Monitor
- CVE-2017-13720In the PatternMatch function in fontfile/fontdir.c in libXfont through 1.5.2 and 2.x before 2.0.2, an attacker with access to an X…28Monitor
- CVE-2007-1352Integer overflow in the FontFileInitTable function in X.Org libXfont before 20070403 allows remote authenticated users to execute arbitrary…15Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libxfont | 1:2.0.1-4 · Debian:12 | Package registry (OSV) |
| opensuse:libXfont | 1.5.4-2.18 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:libXfont | 1.5.1-11.3.12 · SUSE:Linux Enterprise Desktop 12 SP2 | Package registry (OSV) |
| suse:xorg-x11-libs | 7.4-8.26.50.5.3 · SUSE:Linux Enterprise Software Development Kit 11 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.