xar 1.6.1 archive.c xar_unserialize null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in xar 1.6.1. This affects the function xar_unserialize of the file archive.c. Such manipulation leads to null pointer dereference.
This vulnerability is traded as CVE-2017-11124. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability was found in xar 1.6.1. It has been rated as problematic. Affected by this issue is the function xar_unserialize of the file archive.c. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. CVE summarizes:
libxar.so in xar 1.6.1 has a NULL pointer dereference in the xar_unserialize function in archive.c.
The bug was discovered 06/28/2017. The weakness was shared 07/10/2017 (Website). The advisory is shared for download at blogs.gentoo.org. This vulnerability is handled as CVE-2017-11124 since 07/09/2017. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 11 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 entry VDB-103365 is related to this item. Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.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: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
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
06/28/2017 🔍07/09/2017 🔍
07/09/2017 🔍
07/10/2017 🔍
07/10/2017 🔍
12/12/2022 🔍
Sources
Advisory: FEDORA-2020-bbd24dd0cfStatus: Not defined
CVE: CVE-2017-11124 (🔍)
GCVE (CVE): GCVE-0-2017-11124
GCVE (VulDB): GCVE-100-103364
See also: 🔍
Entry
Created: 07/10/2017 09:28Updated: 12/12/2022 09:05
Changes: 07/10/2017 09:28 (57), 10/24/2019 14:44 (1), 12/12/2022 09:05 (3)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.