# CVE-2024-5166: Insecure Direct Object Reference In Looker

> Authenticated users can access metadata from other users sharing the same LookML model, leading to information disclosure.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-x2h9-8xx4-4xfr

## What is CVE-2024-5166?

CVE-2024-5166 is a medium-severity vulnerability in Google Cloud Looker, published on 22 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Insecure Direct Object Reference in Google Cloud's Looker allowed metadata exposure across authenticated Looker users sharing the same LookML model.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2024-5166?

It affects 1 product.


Products: Google Looker.

## How do I fix CVE-2024-5166?

No fix has been published for CVE-2024-5166 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-5166 being exploited?

There is no known exploitation of CVE-2024-5166 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5166 and fix it if it is affected.

What it is: CVE-2024-5166 is a medium-severity vulnerability in Google Cloud Looker, published on 22 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5166 in the wild and no public exploit code.

Affected product: Google Cloud Looker. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-5166/ (Markdown: https://insights.sbomify.com/CVE-2024-5166/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-5166
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-5166
- OSV: https://osv.dev/vulnerability/CVE-2024-5166

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-5166/
Summaries are generated and may contain mistakes; the official description above is the record.