CVE-2024-28120 json
API key leak in codeium-chrome
published 2y ago modified 4mo ago also EUVD-2024-25271
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2024-28120 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/Exafunction/codeium-chrome/security/advisories/GHSA-8c7j-2h97-q63p referenced PoC, tagged "exploit" by a source, unverified
- securitylab.github.com https://securitylab.github.com/advisories/GHSL-2024-027_GHSL-2024-028_codeium-chrome referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- Exafunction codeium-chrome
Classification
References
-
github.com
/Exafunction/codeium-chrome/security/advisories/GHSA-8c7j-2h97-q63p
exploit, vendor-advisory
-
securitylab.github.com
/advisories/GHSL-2024-027_GHSL-2024-028_codeium-chrome
exploit, third-party-advisory
Sources
- CVE List CVE-2024-28120
- NVD CVE-2024-28120
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.