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

> Authenticated attackers can execute arbitrary code via Apache Ant script functionality in WoodWing Elvis DAM.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2024
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-85x9-4hm3-78m9

## What is CVE-2024-37779?

CVE-2024-37779 is a high-severity code injection vulnerability in n/a, published on 23 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WoodWing Elvis DAM v6.98.1 was discovered to contain an authenticated remote command execution (RCE) vulnerability via the Apache Ant script functionality.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-75 (Failure to Sanitize Special Elements into a Different Plane)

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


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

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

## Is CVE-2024-37779 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-37779 is a high-severity code injection vulnerability in n/a, published on 23 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-37779 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-37779/ (Markdown: https://insights.sbomify.com/CVE-2024-37779/index.md)
```

## Sources

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

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