# CVE-2024-23738: Code injection in n/a

> A remote attacker could execute arbitrary code on macOS via specific Node.js inspection settings, though the vendor disputes this claim.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-g343-63vq-2wq6

## What is CVE-2024-23738?

CVE-2024-23738 is a critical code injection vulnerability in n/a, published on 28 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.."

## Which versions are affected by CVE-2024-23738?

It affects 1 product.


Products: Postman Postman.

## How do I fix CVE-2024-23738?

No fix has been published for CVE-2024-23738 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-23738 being exploited?

There is no known exploitation of CVE-2024-23738 in the wild and no public exploit code.

Public exploit code:

- CVE-2024-23738 (github_poc): https://github.com/giovannipajeu1/CVE-2024-23738

## Other vulnerabilities in n/a

- [CVE-2018-17215](https://insights.sbomify.com/CVE-2018-17215/): Information disclosure in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-23738 and fix it if it is affected.

What it is: CVE-2024-23738 is a critical code injection vulnerability in n/a, published on 28 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-23738 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-23738/ (Markdown: https://insights.sbomify.com/CVE-2024-23738/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-23738
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-23738
- OSV: https://osv.dev/vulnerability/CVE-2024-23738

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-23738/
Summaries are generated and may contain mistakes; the official description above is the record.