CVE-2024-45807
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEnvoy is a cloud-native high-performance edge/middle/service proxy. Envoy's 1.31 is using `oghttp` as the default HTTP/2 codec, and there are potential bugs around stream management in the codec. To resolve this Envoy will switch off the `oghttp2` by default. The impact of this issue is that envoy will crash. This issue has been addressed in release version 1.31.2. All users are advised to upgrade. There are no known workarounds for this issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceEnvoy proxy 1.31 uses oghttp as the default HTTP/2 codec, which contains bugs in stream management logic. These bugs can cause Envoy to crash when processing HTTP/2 traffic. The vulnerability was addressed by switching off oghttp2 as the default in version 1.31.2.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.31.0, < 1.31.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Envoy versionRun `envoy --version` or query the admin endpoint `/server_info` to retrieve the running versionAffected if Version is 1.31.0 or 1.31.1 (versions >= 1.31.0 and < 1.31.2)
-
Confirm HTTP/2 traffic is processedReview Envoy listener configurations and verify HTTP/2 protocol is enabled on inbound or outbound listeners. Check listener logs or metrics for http2 traffic.Affected if HTTP/2 traffic is accepted or forwarded by Envoy
-
Verify oghttp2 codec is in useCheck Envoy bootstrap or listener configuration for `codec_type: HTTP/2` or the `oghttp2` codec specification. Query `/config_dump` via admin to inspect active listener codec settings.Affected if The oghttp2 codec is explicitly configured or is the default codec for HTTP/2 listeners
You are affected if your Envoy version is 1.31.0 or 1.31.1 and HTTP/2 traffic is processed with the oghttp2 codec.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.31.2
Upgrade Envoy to version 1.31.2 or later. No workarounds are available; the only remediation is the version upgrade.
Envoy 1.31.2
- Identify current Envoy version using `envoy --version` or checking the deployment manifest
- Stop Envoy service to prevent crashes during upgrade
- Upgrade Envoy to version 1.31.2 using the appropriate package manager or deployment method (e.g., `apt-get install envoy=1.31.2`, Docker image update, or binary replacement)
- Verify the upgrade was successful by running `envoy --version` to confirm version 1.31.2 is installed
- Restart the Envoy service
- Monitor Envoy logs and performance to confirm stability and that the crash issue is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45807 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45807 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data