ytnef 1.9.2 lib/ytnef.c DecompressRTF memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in ytnef 1.9.2. The affected element is the function DecompressRTF in the library lib/ytnef.c. The manipulation results in memory corruption.
This vulnerability is reported as CVE-2017-9474. The attack requires a local approach. No exploit exists.
Details
A vulnerability classified as problematic has been found in ytnef 1.9.2 (Document Reader Software). Affected is the function DecompressRTF in the library lib/ytnef.c. 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 availability. CVE summarizes:
In ytnef 1.9.2, the DecompressRTF function in lib/ytnef.c allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted file.
The bug was discovered 05/24/2017. The weakness was disclosed 06/07/2017 (Website). The advisory is available at blogs.gentoo.org. This vulnerability is traded as CVE-2017-9474 since 06/06/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. Technical details are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 14 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-102041, VDB-102040, VDB-102039 and VDB-102038 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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
05/24/2017 🔍06/06/2017 🔍
06/07/2017 🔍
06/07/2017 🔍
06/07/2017 🔍
12/08/2022 🔍
Sources
Advisory: FEDORA-2019-7d7083b8beStatus: Not defined
CVE: CVE-2017-9474 (🔍)
GCVE (CVE): GCVE-0-2017-9474
GCVE (VulDB): GCVE-100-102042
See also: 🔍
Entry
Created: 06/07/2017 19:50Updated: 12/08/2022 08:25
Changes: 06/07/2017 19:50 (59), 10/14/2019 10:44 (1), 12/08/2022 08:25 (3)
Complete: 🔍
Cache ID: 216:84D:103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.