GNU C Library 2.26 Basename string/basename.c strrchr Argument null termination

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.
3.3$0-$5k0.00

Summaryinfo

A vulnerability was found in GNU C Library 2.26. It has been classified as problematic. This affects the function strrchr of the file string/basename.c of the component Basename. The manipulation as part of Argument leads to null termination. This vulnerability is listed as CVE-2018-8086. There is no available exploit.

Detailsinfo

A vulnerability was found in GNU C Library 2.26 (Software Library) and classified as problematic. This issue affects the function strrchr of the file string/basename.c of the component Basename. The manipulation as part of a Argument leads to a null termination vulnerability. Using CWE to declare the problem leads to CWE-170. The product does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator. Impacted is availability. The summary by CVE is:

The basename implementation in string/basename.c in the GNU C Library (aka glibc or libc6) 2.26 allows attackers to cause a denial of service (segmentation fault), within the assembly code for strrchr, via a crafted argument.

The weakness was presented 03/13/2018 (Website). The advisory is shared at bugzilla.redhat.com. The identification of this vulnerability is CVE-2018-8086 since 03/12/2018. Technical details are known, 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.

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

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.3

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

CVSSv2info

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

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

Exploitinginfo

Class: Null termination
CWE: CWE-170 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined
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

03/12/2018 🔍
03/13/2018 +1 days 🔍
03/13/2018 +0 days 🔍
01/12/2020 +670 days 🔍

Sourcesinfo

Vendor: gnu.org

Advisory: bugzilla.redhat.com
Status: Not defined

CVE: CVE-2018-8086 (🔍)
GCVE (CVE): GCVE-0-2018-8086
GCVE (VulDB): GCVE-100-114413

Entryinfo

Created: 03/13/2018 07:50
Updated: 01/12/2020 17:45
Changes: 03/13/2018 07:50 (42), 01/12/2020 17:45 (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 ▸

Do you need the next level of professionalism?

Upgrade your account now!