Progress Chef InSpec prior 4.56.58/5.22.29 Profile code injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Progress Chef InSpec. This issue affects some unknown processing of the component Profile Handler. Executing a manipulation can lead to code injection. This vulnerability is tracked as CVE-2023-42658. The attack is restricted to local execution. No exploit exists. The affected component should be upgraded.
Details
A vulnerability classified as critical was found in Progress Chef InSpec. This vulnerability affects an unknown part of the component Profile Handler. The manipulation with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Archive command in Chef InSpec prior to 4.56.58 and 5.22.29 allow local command execution via maliciously crafted profile.
The bug was discovered 08/23/2023. The weakness was disclosed 10/31/2023. The advisory is shared for download at docs.chef.io. This vulnerability was named CVE-2023-42658 since 09/12/2023. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.
The vulnerability was handled as a non-public zero-day exploit for at least 69 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 4.56.58 or 5.22.29 eliminates this vulnerability. The upgrade is hosted for download at chef.io. A possible mitigation has been published immediately after the disclosure of the vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 8.8
CNA Vector (Progress Software Corporation): 🔍
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: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Chef InSpec 4.56.58/5.22.29
Timeline
08/23/2023 🔍08/23/2023 🔍
09/12/2023 🔍
10/31/2023 🔍
10/31/2023 🔍
10/31/2023 🔍
01/22/2026 🔍
Sources
Advisory: docs.chef.ioStatus: Confirmed
CVE: CVE-2023-42658 (🔍)
GCVE (CVE): GCVE-0-2023-42658
GCVE (VulDB): GCVE-100-244072
Entry
Created: 10/31/2023 15:28Updated: 01/22/2026 00:33
Changes: 10/31/2023 15:28 (48), 11/24/2023 15:17 (12), 02/10/2024 09:03 (9), 12/29/2024 19:32 (2), 01/22/2026 00:30 (2), 01/22/2026 00:33 (15)
Complete: 🔍
Committer: tas50
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.