# CVE-2024-10653: CHANGING Information Technology IDExpert - OS Command Injection

> Administrators can inject OS commands via an unvalidated parameter in the IDExpert interface, leading to remote code execution on the server.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2024
- **Updated:** 4 Nov 2024
- **Also known as:** GHSA-ww72-4fw2-m2r7

## What is CVE-2024-10653?

CVE-2024-10653 is a high-severity command injection vulnerability in CHANGING Information Technology IDExpert, published on 1 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IDExpert from CHANGING Information Technology does not properly validate a specific parameter in the administrator interface, allowing remote attackers with administrative privileges to inject and execute OS commands on the server.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2024-10653 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10653 is a high-severity command injection vulnerability in CHANGING Information Technology IDExpert, published on 1 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10653 in the wild and no public exploit code.

Affected product: CHANGING Information Technology IDExpert. 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-10653/ (Markdown: https://insights.sbomify.com/CVE-2024-10653/index.md)
```

## Sources

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

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