# CVE-2021-33633: Command Injection in aops-ceres

> Attackers can execute arbitrary OS commands via improper neutralization in aops-ceres, requiring an upgrade to mitigate.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Mar 2024
- **Updated:** 12 Aug 2024
- **Also known as:** GHSA-j32f-6x6r-56fq, OESA-2024-1159

## What is CVE-2021-33633?

CVE-2021-33633 is a high-severity command injection vulnerability in openEuler aops-ceres, published on 23 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in openEuler aops-ceres on Linux allows Command Injection. This vulnerability is associated with program files ceres/function/util.Py.

This issue affects aops-ceres: from 1.3.0 through 1.4.1.

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

## Which versions are affected by CVE-2021-33633?


## How do I fix CVE-2021-33633?

Upgrade to a fixed version.

## Is CVE-2021-33633 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-33633 and fix it if it is affected.

What it is: CVE-2021-33633 is a high-severity command injection vulnerability in openEuler aops-ceres, published on 23 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-33633 in the wild and no public exploit code.

Affected product: openEuler aops-ceres. 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-2021-33633/ (Markdown: https://insights.sbomify.com/CVE-2021-33633/index.md)
```

## Sources

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

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