OSV-2021-430
Stack-buffer-overflow in tvb_memcpy
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31198
Crash type: Stack-buffer-overflow WRITE {*}
Crash state:
tvb_memcpy
composite_memcpy
_tvb_get_nstringz
What each source reports
OSV No score
Stack-buffer-overflow in tvb_memcpy
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31198
Crash type: Stack-buffer-overflow WRITE {*}
Crash state:
tvb_memcpy
composite_memcpy
_tvb_get_nstringz
- Record
OSV-2021-430- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
wiresharkOSS-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-2021-430 is a vulnerability with no CVSS score yet in wireshark, published February 22, 2021. No source lists public exploit code. A source reports a fix.