CyberSecBulletin
CVE-2024-8912NVD status: Analyzed

Looker: Inconsistent Interpretation of HTTP Requests

CVE-2024-8912 is a high-severity inconsistent interpretation of HTTP requests vulnerability in Looker from Google, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 23.12.123, 23.18.117, 24.0.92 as the first without the flaw, so updating Looker to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.19% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Looker to 23.12.123 or 23.18.117 or 24.0.92 or 24.6.77, whichever matches your release line, or a later version.
  2. Update Cloud Looker to 23.12.123 or 23.18.117 or 24.0.92 or 24.6.77, whichever matches your release line, or a later version.
  3. Read the advisory on cloud.google.com for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
GoogleLooker23.12.0 up to, but not including, 23.12.123; 23.18.0 up to, but not including, 23.18.117; 24.0.0 up to, but not including, 24.0.92; 24.6.0 up to, but not including, 24.6.77; 24.8.0 up to, but not including, 24.8.66; 24.10.0 up to, but not including, 24.10.78; 24.12.0 up to, but not including, 24.12.56; 24.14.0 up to, but not including, 24.14.37; and 1 more ranges23.12.123, 23.18.117, 24.0.92, 24.6.77, 24.8.66, 24.10.78
GoogleCloud Looker23.12 up to, but not including, 23.12.123; 23.18 up to, but not including, 23.18.117; 24.0 up to, but not including, 24.0.92; 24.6 up to, but not including, 24.6.77; 24.8 up to, but not including, 24.8.66; 24.10 up to, but not including, 24.10.78; 24.12 up to, but not including, 24.12.56; 24.14 up to, but not including, 24.14.3723.12.123, 23.18.117, 24.0.92, 24.6.77, 24.8.66, 24.10.78

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.08.9HighCNA (google.com)
CVSS 3.17.5HighNVD

Official description

An 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+

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Inconsistent Interpretation of HTTP Requests

The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.

How developers prevent this class of flaw

  • Use a web server that employs a strict HTTP parsing procedure, such as Apache.
  • Terminate the client session after each request.

More Inconsistent Interpretation of HTTP Requests vulnerabilities (CWE-444)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Inconsistent Interpretation of HTTP Requests vulnerabilities

Spotted an error? Tell us.