CVE-2024-8912
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 · uneditedAn HTTP Request Smuggling vulnerability in Looker allowed an unauthorized attacker to capture HTTP responses destined for legitimate users. There are two Looker versions that are hosted by Looker: * Looker (Google Cloud core) was found to be vulnerable. This issue has already been mitigated and our investigation has found no signs of exploitation. * Looker (original) was not vulnerable to this issue. Customer-hosted Looker instances were found to be vulnerable and must be upgraded. This vulnerability has been patched in all supported versions of customer-hosted Looker, which are available on the Looker download page https://download.looker.com/ . For Looker customer-hosted instances, please update to the latest supported version of Looker as soon as possible. The versions below have all been updated to protect from this vulnerability. You can download these versions at the Looker download page: * 23.12 -> 23.12.123+ * 23.18 -> 23.18.117+ * 24.0 -> 24.0.92+ * 24.6 -> 24.6.77+ * 24.8 -> 24.8.66+ * 24.10 -> 24.10.78+ * 24.12 -> 24.12.56+ * 24.14 -> 24.14.37+
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 confidenceHTTP Request Smuggling vulnerability in Looker allows an unauthorized attacker to exploit inconsistencies between front-end and back-end HTTP parsing, enabling them to smuggle requests and capture HTTP responses destined for legitimate users.
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>= 23.12, < 23.12.123>= 23.18, < 23.18.117>= 24.0, < 24.0.92>= 24.6, < 24.6.77>= 24.8, < 24.8.66>= 24.10, < 24.10.78>= 24.12, < 24.12.56>= 24.14, < 24.14.37CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify deployment typeDetermine whether Looker is customer-hosted (on-premises/self-managed) or Google Cloud managed. This vulnerability affects customer-hosted instances; managed cloud instances are patched by Google.Affected if The instance is customer-hosted/on-premises
-
Find installed Looker versionLocate the Looker version number in the admin panel (Admin > Looker > About), Looker logs, or by querying the Looker API endpoint /api/info. Document the exact version string.Affected if Version cannot be determined or is not documented
-
Compare against affected rangesMatch your installed version against these affected ranges: >= 23.12 to < 23.12.123; >= 23.18 to < 23.18.117; >= 24.0 to < 24.0.92; >= 24.6 to < 24.6.77; >= 24.8 to < 24.8.66; >= 24.10 to < 24.10.78; >= 24.12 to < 24.12.56; >= 24.14 to < 24.14.37Affected if Installed version falls within any of these version ranges
-
Verify HTTP front-end/back-end routingConfirm that Looker is deployed behind a reverse proxy or load balancer that handles incoming HTTP requests. The vulnerability exploits inconsistencies between front-end and back-end HTTP parsing, so a direct deployment without a front-end proxy would not exhibit this behavior.Affected if Looker is behind a reverse proxy or load balancer and the version is within affected ranges
A customer-hosted Looker instance with a version matching any of the affected ranges and deployed behind a front-end proxy is vulnerable to HTTP request smuggling.
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 · scoped23.12.12323.18.11724.0.92
Upgrade customer-hosted Looker instances to the patched versions (23.12.123+, 23.18.117+, 24.0.92+, 24.6.77+, 24.8.66+, 24.10.78+, 24.12.56+, or 24.14.37+) available on the Looker download page.
Upgrade to the minimum fixed version for your release branch (23.12.123+, 23.18.117+, 24.0.92+, or 24.6.77+) or the latest supported version (24.14.37+)
- Identify the currently installed Looker version by checking the Looker administration interface or running the appropriate version command
- Navigate to the official Looker download page at https://download.looker.com/ to obtain the appropriate fixed version
- Select the fixed version that corresponds to your current major release: 23.12.123+ for 23.12.x, 23.18.117+ for 23.18.x, 24.0.92+ for 24.0.x, or 24.6.77+ for 24.6.x
- Follow the official Looker upgrade documentation to apply the update to your customer-hosted instance
- After upgrade, verify the Looker version matches the patched release in the administration interface
- Confirm the HTTP Request Smuggling vulnerability is resolved by testing expected behavior
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8912 — 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-8912 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