libsixel 1.8.1 allocator.c sixel_allocator_new resource management
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in libsixel 1.8.1. It has been classified as problematic. Affected is the function sixel_allocator_new
of the file allocator.c. The manipulation leads to resource management.
This vulnerability is traded as CVE-2018-14073. It is possible to launch the attack remotely. There is no exploit available.
It is recommended to upgrade the affected component.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in libsixel 1.8.1 and classified as problematic. This issue affects the function sixel_allocator_new
of the file allocator.c. The manipulation with an unknown input leads to a resource management vulnerability. Using CWE to declare the problem leads to CWE-399. Impacted is availability. The summary by CVE is:
libsixel 1.8.1 has a memory leak in sixel_allocator_new in allocator.c.
The bug was discovered 07/14/2018. The weakness was disclosed 07/15/2018 (Website). It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2018-14073 since 07/15/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 111318 (FreeBSD : Memory leak in different components (efe43d2b-8f35-11e8-b9e8-dcfe074bd614)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l.
Upgrading eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (111318). The entry VDB-121486 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: Resource managementCWE: CWE-399 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
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 |
Nessus ID: 111318
Nessus Name: FreeBSD : Memory leak in different components (efe43d2b-8f35-11e8-b9e8-dcfe074bd614)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
07/14/2018 🔍07/15/2018 🔍
07/15/2018 🔍
07/15/2018 🔍
07/16/2018 🔍
07/24/2018 🔍
07/25/2018 🔍
04/09/2023 🔍
Sources
Advisory: 67Status: Not defined
CVE: CVE-2018-14073 (🔍)
GCVE (CVE): GCVE-0-2018-14073
GCVE (VulDB): GCVE-100-121487
See also: 🔍
Entry
Created: 07/16/2018 09:01 AMUpdated: 04/09/2023 09:46 AM
Changes: 07/16/2018 09:01 AM (66), 03/05/2020 10:27 AM (3), 04/09/2023 09:46 AM (4)
Complete: 🔍
Cache ID: 18:A6A:40
No comments yet. Languages: en.
Please log in to comment.