OSV-2025-81
Segv on unknown address in ndpi_serialize_string_string
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=393404264
Crash type: Segv on unknown address
Crash state:
ndpi_serialize_string_string
ndpi_dpi2json
fuzz_process_packet.c
What each source reports
OSV No score
Segv on unknown address in ndpi_serialize_string_string
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=393404264
Crash type: Segv on unknown address
Crash state:
ndpi_serialize_string_string
ndpi_dpi2json
fuzz_process_packet.c
- Record
OSV-2025-81- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
ndpiOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2025-81 is a vulnerability with no CVSS score yet in ndpi, published February 2, 2025. No source lists public exploit code. A source reports a fix.