OSV-2022-883 Segv on unknown address in HashMgr::add_word
Not scored
Published
Check this codebase for OSV-2022-883 and fix it if it is affected.
What it is: OSV-2022-883 is a vulnerability in hunspell, published on 11 Sep 2022.
Exploitation: There is no known exploitation of OSV-2022-883 in the wild and no public exploit code.
Affected packages and fixed versions:
- hunspell (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-883/ (Markdown: https://insights.sbomify.com/OSV-2022-883/index.md)
A null pointer dereference in HashMgr::add_word can cause a segmentation fault, leading to denial of service in applications using this library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2022-883?
OSV-2022-883 is a vulnerability in hunspell, published on 11 Sep 2022.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=51187
Crash type: Segv on unknown address
Crash state:
HashMgr::add_word
HashMgr::load_tables
HashMgr::HashMgr
Which versions are affected by OSV-2022-883?
1 open source package ship an affected version, including hunspell.
| Package | Affected | Fixed in |
|---|---|---|
hunspell OSS-Fuzz | All versions | None |
How do I fix OSV-2022-883?
No fix has been published for OSV-2022-883 yet. Limit exposure of the affected software until one is available.
Is OSV-2022-883 being exploited?
There is no known exploitation of OSV-2022-883 in the wild and no public exploit code.