Cross-site scripting via unencoded vulnerability details
Published Dec 12, 2024 · Updated Dec 12, 2024
Cross-site scripting in GitLab 17.3 through 17.4.5, 17.5 through 17.5.3, and 17.6 through 17.6.1 allows remote authenticated users to inject script. The vulnerability-details view renders attacker-controlled HTML without sufficient output encoding, allowing script execution when a victim opens the crafted content. Exploitation requires an authenticated user, victim interaction, and disabled CSP; GitLab has not published a more specific consequence.
Summary
What happened
Cross-site scripting in GitLab 17.3 through 17.4.5, 17.5 through 17.5.3, and 17.6 through 17.6.1 allows remote authenticated users to inject script. The vulnerability-details view renders attacker-controlled HTML without sufficient output encoding, allowing script execution when a victim opens the crafted content. Exploitation requires an authenticated user, victim interaction, and disabled CSP; GitLab has not published a more specific consequence.
The record
- CVE
- CVE-2024-8179
- Published
- Dec 12, 2024
- Updated
- Dec 12, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 12, 2024CVE publishedPublication date reported by the CVE source.
- Dec 12, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17.3 <17.4.6
- Affected versionversion=17.5 <17.5.4
- Affected versionversion=17.6 <17.6.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo