OSV-2021-1743 Stack-buffer-overflow in strncat
Not scored
Published
Check this codebase for OSV-2021-1743 and fix it if it is affected.
What it is: OSV-2021-1743 is a memory corruption vulnerability in ghostscript, published on 23 Dec 2021.
Exploitation: There is no known exploitation of OSV-2021-1743 in the wild and no public exploit code.
Affected packages and fixed versions:
- ghostscript (OSS-Fuzz): affected all versions; 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/OSV-2021-1743/ (Markdown: https://insights.sbomify.com/OSV-2021-1743/index.md)
A stack buffer overflow in the PDF parsing library allows attackers to execute arbitrary code or cause a crash via a malicious PDF file.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is OSV-2021-1743?
OSV-2021-1743 is a memory corruption vulnerability in ghostscript, published on 23 Dec 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=42736
Crash type: Stack-buffer-overflow WRITE {*}
Crash state:
strncat
pdf_cmap_open_file
pdfi_read_cmap
Which versions are affected by OSV-2021-1743?
1 open source package ship an affected version, including ghostscript.
| Package | Affected | Fixed in |
|---|---|---|
ghostscript OSS-Fuzz | All versions | None |
How do I fix OSV-2021-1743?
No fix has been published for OSV-2021-1743 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is OSV-2021-1743 being exploited?
There is no known exploitation of OSV-2021-1743 in the wild and no public exploit code.