freetype: parse_charstrings function in type1/t1load.c does not ensure that a font contains a glyph name
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-848-1 | freetype security update |
Debian DSA |
DSA-3839-1 | freetype security update |
EUVD |
EUVD-2016-1429 | The parse_charstrings function in type1/t1load.c in FreeType 2 before 2.7 does not ensure that a font contains a glyph name, which allows remote attackers to cause a denial of service (heap-based buffer over-read) or possibly have unspecified other impact via a crafted file. |
Ubuntu USN |
USN-3237-1 | FreeType vulnerability |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 3.4% (3.367% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.