GNU gcc 11.2 rust-demangle.c demangle_const resource consumption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GNU gcc 11.2. It has been classified as problematic. The impacted element is the function demangle_const of the file libiberty/rust-demangle.c. The manipulation leads to resource consumption.
This vulnerability is documented as CVE-2022-27943. There is not any exploit available.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability, which was classified as problematic, has been found in GNU gcc 11.2. This issue affects the function demangle_const of the file libiberty/rust-demangle.c. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability.
The weakness was released 03/26/2022. It is possible to read the advisory at gcc.gnu.org. The identification of this vulnerability is CVE-2022-27943 since 03/26/2022. Technical details of the vulnerability are known, but there is no available exploit.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at gcc.gnu.org.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-32431). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.gnu.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: gcc.gnu.org
Timeline
03/26/2022 🔍03/26/2022 🔍
03/26/2022 🔍
05/15/2026 🔍
Sources
Vendor: gnu.orgAdvisory: gcc.gnu.org
Status: Confirmed
CVE: CVE-2022-27943 (🔍)
GCVE (CVE): GCVE-0-2022-27943
GCVE (VulDB): GCVE-100-195851
EUVD: 🔍
Entry
Created: 03/26/2022 15:22Updated: 05/15/2026 15:46
Changes: 03/26/2022 15:22 (40), 03/31/2022 06:52 (1), 05/15/2026 15:46 (15)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.