OSV-2021-597 Stack-buffer-overflow in read_mft_common
Not scored
Published
Check this codebase for OSV-2021-597 and fix it if it is affected.
What it is: OSV-2021-597 is a memory corruption vulnerability in skcms, published on 4 Apr 2021.
Exploitation: There is no known exploitation of OSV-2021-597 in the wild and no public exploit code.
Affected packages and fixed versions:
- skcms (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-597/ (Markdown: https://insights.sbomify.com/OSV-2021-597/index.md)
A stack buffer overflow in the skcms library allows attackers to execute arbitrary code or cause a denial of service via crafted image files.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2021-597?
OSV-2021-597 is a memory corruption vulnerability in skcms, published on 4 Apr 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=32837
Crash type: Stack-buffer-overflow WRITE 1
Crash state:
read_mft_common
bool read_tag_mft1<skcms_B2A>
read_b2a
Which versions are affected by OSV-2021-597?
1 open source package ship an affected version, including skcms.
| Package | Affected | Fixed in |
|---|---|---|
skcms OSS-Fuzz | All versions | None |
How do I fix OSV-2021-597?
No fix has been published for OSV-2021-597 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-597 being exploited?
There is no known exploitation of OSV-2021-597 in the wild and no public exploit code.