CVE-2018-20133 Code injection in ymlref
Critical 9.8
Published
Updated
Check this codebase for CVE-2018-20133 and fix it if it is affected.
What it is: CVE-2018-20133 is a critical vulnerability in n/a, published on 17 Dec 2018.
Exploitation: There is no known exploitation of CVE-2018-20133 in the wild and no public exploit code.
Affected packages and fixed versions:
- ymlref (PyPI): affected all versions; no fix listed
- ymlref (PyPI): affected all versions up to 0.1.1; no fix listed
- ymlref (PyPI): affected all versions up to 0.1.1; no fix listed
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-2018-20133/ (Markdown: https://insights.sbomify.com/CVE-2018-20133/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2018-20133?
CVE-2018-20133 is a critical vulnerability in n/a, published on 17 Dec 2018.
Official description
ymlref allows code injection.
Weakness: CWE-94
Which versions are affected by CVE-2018-20133?
3 open source packages ship an affected version, including ymlref. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
ymlref PyPI | All versions | None |
ymlref PyPI | All versions to 0.1.1 | None |
ymlref PyPI | All versions to 0.1.1 | None |
Products include Ymlref Project Ymlref.
How do I fix CVE-2018-20133?
No fix has been published for CVE-2018-20133 yet. Limit exposure of the affected software until one is available.
Is CVE-2018-20133 being exploited?
There is no known exploitation of CVE-2018-20133 in the wild and no public exploit code.
Sources
Also known as GHSA-8r8j-xvfj-36f9, PYSEC-2018-103.