GNU C Library up to 2.29 Regular Expression posix/regexec.c proceed_next_node out-of-bounds

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in GNU C Library up to 2.29. This impacts the function proceed_next_node of the file posix/regexec.c of the component Regular Expression Handler. Performing a manipulation results in out-of-bounds.
This vulnerability is reported as CVE-2019-9169. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in GNU C Library up to 2.29 (Software Library). It has been classified as critical. This affects the function proceed_next_node of the file posix/regexec.c of the component Regular Expression Handler. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In the GNU C Library (aka glibc or libc6) through 2.29, proceed_next_node in posix/regexec.c has a heap-based buffer over-read via an attempted case-insensitive regular-expression match.
The bug was discovered 03/05/2019. The weakness was disclosed 02/26/2019 (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2019-9169 since 02/25/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 13476 (McAfee Web Gateway Multiple Vulnerabilities (SB10278)).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 107160†). The entries VDB-131215, VDB-131216 and VDB-132015 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 2.0
- 2.1
- 2.2
- 2.3
- 2.4
- 2.5
- 2.6
- 2.7
- 2.8
- 2.9
- 2.10
- 2.11
- 2.12
- 2.13
- 2.14
- 2.15
- 2.16
- 2.17
- 2.18
- 2.19
- 2.20
- 2.21
- 2.22
- 2.23
- 2.24
- 2.25
- 2.26
- 2.27
- 2.28
- 2.29
License
Website
- Vendor: https://www.gnu.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: Out-of-boundsCWE: CWE-125 / CWE-119
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 |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: 583dd860d5b833037175247230a328f0050dbfe9
Timeline
02/25/2019 🔍02/25/2019 🔍
02/26/2019 🔍
02/26/2019 🔍
03/05/2019 🔍
07/19/2023 🔍
Sources
Vendor: gnu.orgAdvisory: K54823184⛔
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2019-9169 (🔍)
GCVE (CVE): GCVE-0-2019-9169
GCVE (VulDB): GCVE-100-131217
SecurityFocus: 107160 - GNU glibc Stack Buffer Overflow and Heap Buffer Overflow Vulnerabilities
See also: 🔍
Entry
Created: 02/26/2019 09:36Updated: 07/19/2023 18:16
Changes: 02/26/2019 09:36 (61), 05/13/2020 06:35 (5), 07/19/2023 18:10 (5), 07/19/2023 18:16 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.