OSV-2020-2217
Heap-buffer-overflow in std::__1::pair<int, void*> uWS::HttpParser::fenceAndConsumePostPadded<0>
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28143
Crash type: Heap-buffer-overflow READ {*}
Crash state:
std::__1::pair<int, void*> uWS::HttpParser::fenceAndConsumePostPadded<0>
uWS::HttpParser::consumePostPadded
uWS::HttpContext<false>::init
What each source reports
OSV No score
Heap-buffer-overflow in std::__1::pair<int, void*> uWS::HttpParser::fenceAndConsumePostPadded<0>
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28143
Crash type: Heap-buffer-overflow READ {*}
Crash state:
std::__1::pair<int, void*> uWS::HttpParser::fenceAndConsumePostPadded<0>
uWS::HttpParser::consumePostPadded
uWS::HttpContext<false>::init
- Record
OSV-2020-2217- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
uwebsocketsOSS-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-2020-2217 is a vulnerability with no CVSS score yet in uwebsockets, published December 4, 2020. No source lists public exploit code. A source reports a fix.