In Eclipse Vert.x versions [4.0.0, 4.5.35] or [5.0.0, 5.2.2], when a malicious server keeps sending bytes on an EOL-terminated line (not…
In Eclipse Vert.x versions [4.0.0, 4.5.35] or [5.0.0, 5.2.2], when a malicious server keeps sending bytes on an EOL-terminated line (not length-prefixed, for example a simple string [1]), we'll keep growing the buffer without bounds, eventually leading to an OOM. We need to have a configurable limit for EOL-terminated lines. If a malicious server sends a specially crafted RESP response (for example a bulk string [2] with missing CRLF trailer), the parser enters an infinite loop where it keeps parsing the same buffer and pushing the same response to the caller, which may lead e.g. to an OOM if the consumer just buffers the responses. We must fix the parser to avoid this infinite looping.
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- Eclipse Foundation
- Product
- Eclipse Vert.x
- CVSS v3.1
- 5.9 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- Exposure class
- Web platform
- NVD status
- Deferred
Why it ranks 23 (Routine)
- CVSS v3.1 5.9 medium
- Product class: web platform
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.