Every CVE Search/ Get API key

OSV-2020-150

Segv on unknown address in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch

No scoreFix available

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20457

Crash type: Segv on unknown address
Crash state:
std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch
std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch
wabt::BinaryReaderIR::OnDataSymbol

What each source reports

OSV No score

Segv on unknown address in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20457

Crash type: Segv on unknown address
Crash state:
std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch
std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch
wabt::BinaryReaderIR::OnDataSymbol
Record
OSV-2020-150
Updated
2026-11-02

Affected packages

Affected packages
PackageAffectedFixed
wabt
OSS-Fuzz
Listed versions, plus commit ranges
1.0.141.0.15
None known

History

History
RecordedChangedSources
first indexedOSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

OSV-2020-150 is a vulnerability with no CVSS score yet in wabt, published June 24, 2020. No source lists public exploit code. A source reports a fix.

References

MoveEnter Open