Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #8 on issue 3219 by
monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm:
Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3219#c8
Comment #7 on issue 3219 by
monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm:
Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3219#c7
ClusterFuzz has detected this issue as fixed in range
Comment #6 on issue 3219 by v...@apple.com: llvm: Heap-buffer-overflow in
llvm::StringMapImpl::LookupBucketFor
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3219#c6
Fixed in r316357. The issue was in llvm 5.0. The root cause was a bug in
Wasm object file parsing.
--
You received
Updates:
Cc: v...@apple.com
Comment #5 on issue 3219 by
monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm:
Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3219#c5
(No comment was entered for this change.)