Every CVE Search/ Get API key

OSV-2020-823

Object-size in std::__1::vector<wabt::DataSegment*, std::__1::allocator<wabt::DataSegment*> >::

No scoreFix available

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

Crash type: Object-size
Crash state:
std::__1::vector<wabt::DataSegment*, std::__1::allocator<wabt::DataSegment*> >::
wabt::BinaryReaderIR::OnDataSymbol
wabt::BinaryReader::ReadLinkingSection

What each source reports

OSV No score

Object-size in std::__1::vector<wabt::DataSegment*, std::__1::allocator<wabt::DataSegment*> >::

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

Crash type: Object-size
Crash state:
std::__1::vector<wabt::DataSegment*, std::__1::allocator<wabt::DataSegment*> >::
wabt::BinaryReaderIR::OnDataSymbol
wabt::BinaryReader::ReadLinkingSection
Record
OSV-2020-823
Updated
2026-11-02

Affected packages

Affected packages
PackageAffectedFixed
wabt
OSS-Fuzz
Listed versions, plus commit ranges
1.0.141.0.151.0.161.0.171.0.181.0.19gh-actions-testgh-actions-test2
None known

History

History
RecordedChangedSources
first indexedOSV

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

In short

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

References

MoveEnter Open