CVE-2021-3533 This vulnerability does not meet the criteria for a security vulnerability
Not scored
Published
Updated
Check this codebase for CVE-2021-3533 and fix it if it is affected.
What it is: CVE-2021-3533 is a vulnerability in ansible, published on 9 Jun 2021.
Exploitation: There is no known exploitation of CVE-2021-3533 in the wild and no public exploit code.
Affected packages and fixed versions:
- ansible (PyPI): affected all versions; fixed in 3.0.0
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-3533/ (Markdown: https://insights.sbomify.com/CVE-2021-3533/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2021-3533?
CVE-2021-3533 is a vulnerability in ansible, published on 9 Jun 2021.
Official description
This vulnerability does not meet the criteria for a security vulnerability
Which versions are affected by CVE-2021-3533?
1 open source package ship an affected version, including ansible.
| Package | Affected | Fixed in |
|---|---|---|
ansible PyPI | All versions | 3.0.0 |
How do I fix CVE-2021-3533?
Upgrade ansible to 3.0.0 or later.
Is CVE-2021-3533 being exploited?
There is no known exploitation of CVE-2021-3533 in the wild and no public exploit code.
Sources
Also known as PYSEC-2021-126, UBUNTU-CVE-2021-3533.