Every CVE Search/ Get API key

OSV-2022-409

Heap-buffer-overflow in std::__1::__tree_node_base<void*>*& std::__1::__tree<std::__1::__value_type<std:

No scoreFix available

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

Crash type: Heap-buffer-overflow READ 1
Crash state:
std::__1::__tree_node_base<void*>*& std::__1::__tree<std::__1::__value_type<std:
std::__1::pair<std::__1::__tree_iterator<std::__1::__value_type<std::__1::basic_
nlohmann::detail::binary_reader<nlohmann::basic_json<std::__1::map, std::__1::ve

What each source reports

OSV No score

Heap-buffer-overflow in std::__1::__tree_node_base<void*>*& std::__1::__tree<std::__1::__value_type<std:

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

Crash type: Heap-buffer-overflow READ 1
Crash state:
std::__1::__tree_node_base<void*>*& std::__1::__tree<std::__1::__value_type<std:
std::__1::pair<std::__1::__tree_iterator<std::__1::__value_type<std::__1::basic_
nlohmann::detail::binary_reader<nlohmann::basic_json<std::__1::map, std::__1::ve
Record
OSV-2022-409
Updated
2026-11-02

Affected packages

Affected packages
PackageAffectedFixed
json
OSS-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

History
RecordedChangedSources
first indexedOSV

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

In short

OSV-2022-409 is a vulnerability with no CVSS score yet in json, published May 12, 2022. No source lists public exploit code. A source reports a fix.

References

MoveEnter Open