re2c 1.3 parse/scanner.cc Scanner::fill out-of-bounds write
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in re2c 1.3. It has been rated as critical. Affected by this issue is the function Scanner::fill
of the file parse/scanner.cc. The manipulation leads to out-of-bounds write.
This vulnerability is handled as CVE-2020-11958. The attack needs to be approached locally. There is no exploit available.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability was found in re2c 1.3. It has been declared as critical. Affected by this vulnerability is the function Scanner::fill
of the file parse/scanner.cc. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
re2c 1.3 has a heap-based buffer overflow in Scanner::fill in parse/scanner.cc via a long lexeme.
The weakness was shared 04/21/2020 (oss-sec). It is possible to read the advisory at openwall.com. This vulnerability is known as CVE-2020-11958 since 04/20/2020. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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-bounds writeCWE: CWE-787 / CWE-119
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
04/20/2020 🔍04/21/2020 🔍
04/22/2020 🔍
05/06/2025 🔍
Sources
Advisory: c4603ba5ce229db83a2a4fb93e6d4b4e3ec3776aStatus: Confirmed
CVE: CVE-2020-11958 (🔍)
GCVE (CVE): GCVE-0-2020-11958
GCVE (VulDB): GCVE-100-154159
Entry
Created: 04/22/2020 10:07 AMUpdated: 05/06/2025 03:44 PM
Changes: 04/22/2020 10:07 AM (37), 04/22/2020 10:12 AM (17), 06/01/2024 11:17 AM (18), 06/01/2024 11:24 AM (1), 05/06/2025 03:44 PM (9)
Complete: 🔍
Cache ID: 18:35E:40
No comments yet. Languages: en.
Please log in to comment.