FontForge OTF File parsettf.c ValidatePostScriptFontName memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in FontForge. Affected by this issue is the function ValidatePostScriptFontName of the file parsettf.c of the component OTF File Handler. The manipulation results in memory corruption.
This vulnerability is cataloged as CVE-2017-11573. The attack must be initiated from a local position. There is no exploit available.
Details
A vulnerability was found in FontForge (unknown version). It has been classified as critical. Affected is the function ValidatePostScriptFontName of the file parsettf.c of the component OTF File Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
FontForge 20161012 is vulnerable to a buffer over-read in ValidatePostScriptFontName (parsettf.c) resulting in DoS or code execution via a crafted otf file.
The bug was discovered 07/23/2017. The weakness was shared 07/23/2017 (Website). The advisory is shared for download at github.com. This vulnerability is traded as CVE-2017-11573 since 07/23/2017. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-104428, VDB-104427, VDB-104426 and VDB-104425 are related to this item. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/23/2017 🔍07/23/2017 🔍
07/23/2017 🔍
07/23/2017 🔍
07/24/2017 🔍
12/13/2022 🔍
Sources
Product: github.comAdvisory: 3098
Status: Not defined
CVE: CVE-2017-11573 (🔍)
GCVE (CVE): GCVE-0-2017-11573
GCVE (VulDB): GCVE-100-104424
See also: 🔍
Entry
Created: 07/24/2017 12:18Updated: 12/13/2022 17:15
Changes: 07/24/2017 12:18 (57), 10/31/2019 17:29 (1), 12/13/2022 17:15 (3)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.