# CVE-2024-24890: Command injection in ioprobe of gala-gopher

> An attacker can execute arbitrary OS commands via improper neutralization in the ioprobe component of openEuler gala-gopher.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2024
- **Updated:** 12 Aug 2024
- **Also known as:** GHSA-q35v-9jf2-h48r, OESA-2024-1277, OESA-2024-1278, OESA-2024-1279

## What is CVE-2024-24890?

CVE-2024-24890 is a high-severity command injection vulnerability in openEuler gala-gopher, published on 25 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in openEuler gala-gopher on Linux allows Command Injection. This vulnerability is associated with program files https://gitee.Com/openeuler/gala-gopher/blob/master/src/probes/extends/ebpf.Probe/src/ioprobe/ioprobe.C.

This issue affects gala-gopher: through 1.0.2.

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

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


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

Upgrade to a fixed version.

## Is CVE-2024-24890 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-24890 is a high-severity command injection vulnerability in openEuler gala-gopher, published on 25 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-24890 in the wild and no public exploit code.

Affected product: openEuler gala-gopher. 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-24890/ (Markdown: https://insights.sbomify.com/CVE-2024-24890/index.md)
```

## Sources

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

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