OSV-2022-319 Heap-buffer-overflow in LoadPSD
Not scored
Published
Check this codebase for OSV-2022-319 and fix it if it is affected.
What it is: OSV-2022-319 is a memory corruption vulnerability in kimageformats, published on 8 Apr 2022.
Exploitation: There is no known exploitation of OSV-2022-319 in the wild and no public exploit code.
Affected packages and fixed versions:
- kimageformats (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-2022-319/ (Markdown: https://insights.sbomify.com/OSV-2022-319/index.md)
A heap buffer overflow in the LoadPSD function allows attackers to cause denial of service or potentially execute code via malicious PSD files.
- 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-2022-319?
OSV-2022-319 is a memory corruption vulnerability in kimageformats, published on 8 Apr 2022.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46437
Crash type: Heap-buffer-overflow WRITE 2
Crash state:
LoadPSD
PSDHandler::read
kimgio_fuzzer.cc
Which versions are affected by OSV-2022-319?
1 open source package ship an affected version, including kimageformats.
| Package | Affected | Fixed in |
|---|---|---|
kimageformats OSS-Fuzz | All versions | None |
How do I fix OSV-2022-319?
No fix has been published for OSV-2022-319 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-2022-319 being exploited?
There is no known exploitation of OSV-2022-319 in the wild and no public exploit code.