OSV-2017-116 Use-after-poison in rawspeed::OrfDecoder::decodeCompressed
Not scored
Published
Check this codebase for OSV-2017-116 and fix it if it is affected.
What it is: OSV-2017-116 is an use after free vulnerability in librawspeed, published on 13 Jan 2021.
Exploitation: There is no known exploitation of OSV-2017-116 in the wild and no public exploit code.
Affected packages and fixed versions:
- librawspeed (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-2017-116/ (Markdown: https://insights.sbomify.com/OSV-2017-116/index.md)
A use-after-poison vulnerability in the rawspeed library allows attackers to cause a denial of service or potentially execute code via crafted ORF images.
- 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-2017-116?
OSV-2017-116 is an use after free vulnerability in librawspeed, published on 13 Jan 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3012
Crash type: Use-after-poison WRITE 2
Crash state:
rawspeed::OrfDecoder::decodeCompressed
rawspeed::OrfDecoder::decodeRawInternal
rawspeed::RawDecoder::decodeRaw
Which versions are affected by OSV-2017-116?
1 open source package ship an affected version, including librawspeed.
| Package | Affected | Fixed in |
|---|---|---|
librawspeed OSS-Fuzz | All versions | None |
How do I fix OSV-2017-116?
No fix has been published for OSV-2017-116 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is OSV-2017-116 being exploited?
There is no known exploitation of OSV-2017-116 in the wild and no public exploit code.