# CVE-2021-33632: TOCTOU Race Condition problem in iSulad

> A TOCTOU race condition in iSulad allows attackers to exploit timing gaps, potentially leading to privilege escalation or code execution.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/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:** 3 Aug 2024
- **Also known as:** GHSA-mrfq-6jmf-4q53, OESA-2024-1287, OESA-2024-1289, OESA-2024-1290, OESA-2024-1307

## What is CVE-2021-33632?

CVE-2021-33632 is a high-severity vulnerability in openEuler iSulad, 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

Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in openEuler iSulad on Linux allows Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions. This vulnerability is associated with program files https://gitee.Com/openeuler/iSulad/blob/master/src/cmd/isulad/main.C.

This issue affects iSulad: 2.0.18-13, from 2.1.4-1 through 2.1.4-2.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

Apply the vendor's patch.

## Is CVE-2021-33632 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-33632 is a high-severity vulnerability in openEuler iSulad, 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-2021-33632 in the wild and no public exploit code.

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

## Sources

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

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