# CVE-2024-10919: didi Super-Jacoco triggerUnitCover os command injection

> Remote attackers can execute arbitrary OS commands via the uuid parameter in the triggerUnitCover endpoint of didi Super-Jacoco.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **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:** 6 Nov 2024
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-7v36-f3gj-qcg5

## What is CVE-2024-10919?

CVE-2024-10919 is a medium-severity command injection vulnerability in didi Super-Jacoco, published on 6 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in didi Super-Jacoco 1.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /cov/triggerUnitCover. The manipulation of the argument uuid leads to os command injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Didi Super-Jacoco.

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

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

## Is CVE-2024-10919 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10919 is a medium-severity command injection vulnerability in didi Super-Jacoco, published on 6 Nov 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-10919 exists.

Affected product: didi Super-Jacoco. 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-10919/ (Markdown: https://insights.sbomify.com/CVE-2024-10919/index.md)
```

## Sources

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

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