OSV-2018-293 Use-of-uninitialized-value in pdf_load_version
Not scored
Published
Check this codebase for OSV-2018-293 and fix it if it is affected.
What it is: OSV-2018-293 is a vulnerability in mupdf, published on 15 Jan 2021.
Exploitation: There is no known exploitation of OSV-2018-293 in the wild and no public exploit code.
Affected packages and fixed versions:
- mupdf (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-2018-293/ (Markdown: https://insights.sbomify.com/OSV-2018-293/index.md)
An attacker can cause a denial of service by providing a malformed PDF file that triggers the use of an uninitialized value during parsing.
- 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-2018-293?
OSV-2018-293 is a vulnerability in mupdf, published on 15 Jan 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5496
Crash type: Use-of-uninitialized-value
Crash state:
pdf_load_version
pdf_init_document
pdf_open_document_with_stream
Which versions are affected by OSV-2018-293?
1 open source package ship an affected version, including mupdf.
| Package | Affected | Fixed in |
|---|---|---|
mupdf OSS-Fuzz | All versions | None |
How do I fix OSV-2018-293?
No fix has been published for OSV-2018-293 yet. Limit exposure of the affected software until one is available.
Is OSV-2018-293 being exploited?
There is no known exploitation of OSV-2018-293 in the wild and no public exploit code.