# CVE-2023-36467: AWS data.all vulnerable to RCE through user injection of Python Commands


- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Jun 2023
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-m922-chh7-8qcr

## What is CVE-2023-36467?

CVE-2023-36467 is a high-severity vulnerability in awslabs aws-dataall, published on 28 Jun 2023. 

### Official description

AWS data.all is an open source development framework to help users build a data marketplace on Amazon Web Services. data.all versions 1.2.0 through 1.5.1 do not prevent remote code execution when a user injects Python commands into the ‘Template’ field when configuring a data pipeline. The issue can only be triggered by authenticated users. A fix for this issue is available in data.all version 1.5.2 and later. There is no recommended work around.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2023-36467?

It affects 1 product.


Products: Amazon Aws-Dataall.

## How do I fix CVE-2023-36467?

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

## Is CVE-2023-36467 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-36467 and fix it if it is affected.

What it is: CVE-2023-36467 is a high-severity vulnerability in awslabs aws-dataall, published on 28 Jun 2023. 
Exploitation: There is no known exploitation of CVE-2023-36467 in the wild and no public exploit code.

Affected product: awslabs aws-dataall. 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-2023-36467/ (Markdown: https://insights.sbomify.com/CVE-2023-36467/index.md)
```

## Sources

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

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