CVE-2024-4099: Improper Encoding or Escaping of Output in GitLab
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.
Other sources
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’ve allowed an attacker to hide prompt injection. This is a low severity issue (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N, 3.1). It is now mitigated in the latest release and is assigned CVE-2024-4099.
— GitLab
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2024-4099?
CVE-2024-4099 has been assessed as a medium severity vulnerability.
How do I fix CVE-2024-4099?
To mitigate CVE-2024-4099, upgrade your GitLab EE instance to version 17.2.8 or later, 17.3.4 or later, or 17.4.1 or later.
Which versions of GitLab are affected by CVE-2024-4099?
CVE-2024-4099 affects GitLab EE versions from 16.0 up to but not including 17.2.8, from 17.3 up to but not including 17.3.4, and version 17.4.0.
What type of vulnerability is CVE-2024-4099?
CVE-2024-4099 is a prompt injection vulnerability that allows attackers to exploit unsanitized content in GitLab's AI feature.
Is there a workaround for CVE-2024-4099?
There are currently no publicly documented workarounds for CVE-2024-4099; updating to a fixed version is recommended.