OSV-2023-1093 Stack-buffer-overflow in ndpi_handle_rule
Not scored
Published
Check this codebase for OSV-2023-1093 and fix it if it is affected.
What it is: OSV-2023-1093 is a memory corruption vulnerability in ndpi, published on 31 Oct 2023.
Exploitation: There is no known exploitation of OSV-2023-1093 in the wild and no public exploit code.
Affected packages and fixed versions:
- ndpi (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-2023-1093/ (Markdown: https://insights.sbomify.com/OSV-2023-1093/index.md)
A stack buffer overflow in the nDPI library allows attackers to execute arbitrary code or cause denial of service via crafted protocol 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-2023-1093?
OSV-2023-1093 is a memory corruption vulnerability in ndpi, published on 31 Oct 2023.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63746
Crash type: Stack-buffer-overflow WRITE {*}
Crash state:
ndpi_handle_rule
ndpi_load_protocols_file_fd
fuzz_filecfg_protocols.c
Which versions are affected by OSV-2023-1093?
1 open source package ship an affected version, including ndpi.
| Package | Affected | Fixed in |
|---|---|---|
ndpi OSS-Fuzz | All versions | None |
How do I fix OSV-2023-1093?
No fix has been published for OSV-2023-1093 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-2023-1093 being exploited?
There is no known exploitation of OSV-2023-1093 in the wild and no public exploit code.