CVE-2024-4099 Improper Encoding or Escaping of Output in GitLab
Attackers can exploit unsanitized AI input to hide prompt injections, potentially leading to code execution or security bypasses in GitLab EE.
- 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
- None listed
What is CVE-2024-4099?
CVE-2024-4099 is a low-severity code injection vulnerability in Gitlab Gitlab, published on 26 Sep 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
An issue has been discovered in GitLab EE affecting all versions starting from 16.0 prior to 17.2.8, from 17.3 prior to 17.3.4, and from 17.4 prior to 17.4.1. An AI feature was found to read unsanitized content in a way that could have allowed an attacker to hide prompt injection.
Weakness: CWE-116
Which versions are affected by CVE-2024-4099?
It affects 1 product.
Products include Gitlab Gitlab.
How do I fix CVE-2024-4099?
No fix has been published for CVE-2024-4099 yet. Limit exposure of the affected software until one is available.
Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.
Is CVE-2024-4099 being exploited?
There is no known exploitation of CVE-2024-4099 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as GHSA-8qr9-mc3w-88c6.