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

> Remote attackers can execute arbitrary code and escalate privileges by uploading a crafted file to the upload.php component in GNU Savane.

- **Severity:** High 7.6 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2024
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-rhmf-g96x-3g22

## What is CVE-2024-29399?

CVE-2024-29399 is a high-severity code injection vulnerability in n/a, published on 11 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in GNU Savane v.3.13 and before, allows a remote attacker to execute arbitrary code and escalate privileges via a crafted file to the upload.php component.

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

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

It affects 1 product.


Products: Gnu Savane.

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

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

## Is CVE-2024-29399 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29399 exists.

Public exploit code:

- CVE-2024-29399 reference (github_poc): https://github.com/ally-petitt/CVE-2024-29399

## Other vulnerabilities in n/a

- [CVE-2024-27632](https://insights.sbomify.com/CVE-2024-27632/): Privilege escalation in n/a (high 8.8)
- [CVE-2024-27630](https://insights.sbomify.com/CVE-2024-27630/): Missing authorization in n/a (high 7.5)
- [CVE-2024-27631](https://insights.sbomify.com/CVE-2024-27631/): Cross-site request forgery in n/a (medium 6.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29399 is a high-severity code injection vulnerability in n/a, published on 11 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29399 exists.

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-29399/ (Markdown: https://insights.sbomify.com/CVE-2024-29399/index.md)
```

## Sources

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

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