# CVE-2024-28120: API key leak in codeium-chrome

> A malicious website can steal the user's Codeium API key via the extension's service worker, allowing impersonation on the backend server.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Mar 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-8c7j-2h97-q63p

## What is CVE-2024-28120?

CVE-2024-28120 is a medium-severity vulnerability in Exafunction codeium-chrome, published on 11 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

codeium-chrome is an open source code completion plugin for the chrome web browser. The service worker of the codeium-chrome extension doesn't check the sender when receiving an external message. This allows an attacker to host a website that will steal the user's Codeium api-key, and thus impersonate the user on the backend autocomplete server. This issue has not been addressed. Users are advised to monitor the usage of their API key.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Codeium Codeium.

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

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

## Is CVE-2024-28120 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28120 is a medium-severity vulnerability in Exafunction codeium-chrome, published on 11 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-28120 in the wild and no public exploit code.

Affected product: Exafunction codeium-chrome. 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-28120/ (Markdown: https://insights.sbomify.com/CVE-2024-28120/index.md)
```

## Sources

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

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