pkgconf up to 1.9.3 PC File libpkgconf/tuple.c pkgconf_tuple_parse denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in pkgconf up to 1.9.3. The affected element is the function pkgconf_tuple_parse of the file libpkgconf/tuple.c of the component PC File Handler. The manipulation leads to an unknown weakness.
This vulnerability is uniquely identified as CVE-2023-24056. The attack is possible to be carried out remotely. No exploit exists.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in pkgconf up to 1.9.3 and classified as problematic. This issue affects the function pkgconf_tuple_parse of the file libpkgconf/tuple.c of the component PC File Handler. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability. The summary by CVE is:
In pkgconf through 1.9.3, variable duplication can cause unbounded string expansion due to incorrect checks in libpkgconf/tuple.c:pkgconf_tuple_parse. For example, a .pc file containing a few hundred bytes can expand to one billion bytes.
The weakness was disclosed 01/22/2023. The advisory is shared at nullprogram.com. The identification of this vulnerability is CVE-2023-24056 since 01/22/2023. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Applying the patch 628b2b2bafa5d3a2017193ddf375093e70666059 is able to eliminate this problem. The bugfix is ready for download at gitea.treehouse.systems.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 628b2b2bafa5d3a2017193ddf375093e70666059
Timeline
01/22/2023 🔍01/22/2023 🔍
01/22/2023 🔍
04/02/2025 🔍
Sources
Advisory: 628b2b2bafa5d3a2017193ddf375093e70666059Status: Confirmed
CVE: CVE-2023-24056 (🔍)
GCVE (CVE): GCVE-0-2023-24056
GCVE (VulDB): GCVE-100-219137
Entry
Created: 01/22/2023 11:40Updated: 04/02/2025 23:31
Changes: 01/22/2023 11:40 (40), 02/18/2023 09:57 (1), 02/18/2023 10:00 (11), 04/02/2025 23:31 (15)
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.