libsvg2 up to 2012-10-19 svg_string.c svgGetNextPathField resource management

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.4$0-$5k0.00

Summaryinfo

A vulnerability was found in libsvg2 up to 2012-10-19. It has been rated as problematic. This impacts the function svgGetNextPathField of the file svg_string.c. The manipulation leads to resource management. This vulnerability is uniquely identified as CVE-2018-17332. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in libsvg2 up to 2012-10-19. It has been rated as problematic. This issue affects the function svgGetNextPathField of the file svg_string.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:

An issue was discovered in libsvg2 through 2012-10-19. The svgGetNextPathField function in svg_string.c returns its input pointer in certain circumstances, which might result in a memory leak caused by wasteful malloc calls.

The bug was discovered 09/12/2018. The weakness was disclosed 09/22/2018 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2018-17332 since 09/22/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 are known, but no exploit is available.

The vulnerability was handled as a non-public zero-day exploit for at least 10 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-124399 and VDB-124398 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.4

VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Resource management
CWE: CWE-399 / 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

09/12/2018 🔍
09/22/2018 +9 days 🔍
09/22/2018 +0 days 🔍
09/22/2018 +0 days 🔍
09/23/2018 +1 days 🔍
03/26/2020 +550 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2018-17332 (🔍)
GCVE (CVE): GCVE-0-2018-17332
GCVE (VulDB): GCVE-100-124397
See also: 🔍

Entryinfo

Created: 09/23/2018 08:22
Updated: 03/26/2020 16:27
Changes: 09/23/2018 08:22 (57), 03/26/2020 16:27 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!