OSV-2020-573
UNKNOWN READ in (__has_construct<std::__1::allocator<unsigned
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14479
Crash type: UNKNOWN READ
Crash state:
(__has_construct<std::__1::allocator<unsigned
std::__1::enable_if<__is_forward_iterator<unsigned char const*>::value, void>::t
std::__1::vector<unsigned char, std::__1::allocator<unsigned char> >::vector<uns
What each source reports
OSV No score
UNKNOWN READ in (__has_construct<std::__1::allocator<unsigned
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14479
Crash type: UNKNOWN READ
Crash state:
(__has_construct<std::__1::allocator<unsigned
std::__1::enable_if<__is_forward_iterator<unsigned char const*>::value, void>::t
std::__1::vector<unsigned char, std::__1::allocator<unsigned char> >::vector<uns
- Record
OSV-2020-573- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
wpantundOSS-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-2020-573 is a vulnerability with no CVSS score yet in wpantund, published July 1, 2020. No source lists public exploit code. A source reports a fix.