Postman up to 10.22 on macOS Setting RunAsNode/enableNodeClilnspectArguments privilege escalation ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Postman up to 10.22 on macOS. This impacts an unknown function of the component Setting Handler. Executing a manipulation of the argument RunAsNode/enableNodeClilnspectArguments can lead to an unknown weakness. This vulnerability is registered as CVE-2024-23738. It is possible to launch the attack remotely. No exploit is available. There is ongoing doubt regarding the real existence of this vulnerability.
Details
A vulnerability was found in Postman up to 10.22 on macOS. It has been declared as critical. This vulnerability affects an unknown code block of the component Setting Handler. The manipulation of the argument RunAsNode/enableNodeClilnspectArguments with an unknown input leads to a unknown weakness. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
An issue in Postman version 10.22 and before on macOS allows a remote attacker to execute arbitrary code via the RunAsNode and enableNodeClilnspectArguments settings. NOTE: the vendor states "we dispute the report's accuracy ... the configuration does not enable remote code execution.."
The weakness was published 01/28/2024. The advisory is available at github.com. This vulnerability was named CVE-2024-23738 since 01/21/2024. Technical details are known, but there is no available exploit.
The real existence of this vulnerability is still doubted at the moment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
- 10.0
- 10.1
- 10.2
- 10.3
- 10.4
- 10.5
- 10.6
- 10.7
- 10.8
- 10.9
- 10.10
- 10.11
- 10.12
- 10.13
- 10.14
- 10.15
- 10.16
- 10.17
- 10.18
- 10.19
- 10.20
- 10.21
- 10.22
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
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: 🔍
Exploiting
Class: Privilege escalationCWE: Unknown
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/21/2024 🔍01/28/2024 🔍
01/28/2024 🔍
08/02/2024 🔍
Sources
Advisory: github.comStatus: Not defined
Disputed: 🔍
CVE: CVE-2024-23738 (🔍)
GCVE (CVE): GCVE-0-2024-23738
GCVE (VulDB): GCVE-100-252250
Entry
Created: 01/28/2024 09:49Updated: 08/02/2024 12:36
Changes: 01/28/2024 09:49 (37), 02/21/2024 08:12 (11), 02/26/2024 11:32 (2), 03/06/2024 11:47 (1), 08/02/2024 12:36 (15)
Complete: 🔍
Committer: harshit.kochar
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.