OSV-2022-168
Heap-buffer-overflow in fmt::v8::detail::big_decimal_fp fmt::v8::detail::write_padded<
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=44791
Crash type: Heap-buffer-overflow WRITE 1
Crash state:
fmt::v8::detail::big_decimal_fp fmt::v8::detail::write_padded<
std::__1::back_insert_iterator<fmt::v8::basic_memory_buffer<char, 500ul, std::__
std::__1::back_insert_iterator<fmt::v8::basic_memory_buffer<char, 500ul, std::__
What each source reports
OSV No score
Heap-buffer-overflow in fmt::v8::detail::big_decimal_fp fmt::v8::detail::write_padded<
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=44791
Crash type: Heap-buffer-overflow WRITE 1
Crash state:
fmt::v8::detail::big_decimal_fp fmt::v8::detail::write_padded<
std::__1::back_insert_iterator<fmt::v8::basic_memory_buffer<char, 500ul, std::__
std::__1::back_insert_iterator<fmt::v8::basic_memory_buffer<char, 500ul, std::__
- Record
OSV-2022-168- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
fmtOSS-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-2022-168 is a vulnerability with no CVSS score yet in fmt, published February 19, 2022. No source lists public exploit code. A source reports a fix.