OSV-2021-620 Segv on unknown address in dwg_free_summaryinfo
Not scored
Published
Check this codebase for OSV-2021-620 and fix it if it is affected.
What it is: OSV-2021-620 is a vulnerability in libredwg, published on 10 Apr 2021.
Exploitation: There is no known exploitation of OSV-2021-620 in the wild and no public exploit code.
Affected packages and fixed versions:
- libredwg (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-620/ (Markdown: https://insights.sbomify.com/OSV-2021-620/index.md)
A null pointer dereference in the DWG file parser allows attackers to cause a denial of service via crafted 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-620?
OSV-2021-620 is a vulnerability in libredwg, published on 10 Apr 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33059
Crash type: Segv on unknown address
Crash state:
dwg_free_summaryinfo
dwg_free
llvmfuzz.c
Which versions are affected by OSV-2021-620?
1 open source package ship an affected version, including libredwg.
| Package | Affected | Fixed in |
|---|---|---|
libredwg OSS-Fuzz | All versions | None |
How do I fix OSV-2021-620?
No fix has been published for OSV-2021-620 yet. Limit exposure of the affected software until one is available.
Is OSV-2021-620 being exploited?
There is no known exploitation of OSV-2021-620 in the wild and no public exploit code.