# CVE-2024-42017: Command injection in n/a

> Attackers can execute arbitrary commands with system privileges on the endpoint hosting the application without authentication if the web interface is remotely accessible.

- **Severity:** Critical 10.0 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2024
- **Updated:** 29 Oct 2024
- **Also known as:** GHSA-hjpg-cfqw-g6jv

## What is CVE-2024-42017?

CVE-2024-42017 is a critical command injection vulnerability in n/a, published on 30 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Atos Eviden iCare 2.7.1 through 2.7.11. The application exposes a web interface locally. In the worst-case scenario, if the application is remotely accessible, it allows an attacker to execute arbitrary commands with system privilege on the endpoint hosting the application, without any authentication.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2024-42017 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42017 is a critical command injection vulnerability in n/a, published on 30 Sep 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-42017 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-42017/ (Markdown: https://insights.sbomify.com/CVE-2024-42017/index.md)
```

## Sources

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

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