Background-job denial of service via artifact metadata
Published Jan 28, 2025 · Updated Jan 28, 2025
Infinite loop in GitLab CE/EE allows remote authenticated users to make background jobs unresponsive via CI artifact metadata processing. GitLab identifies CI artifact metadata processing as the affected locus but has not published the loop condition or the metadata operation that fails to terminate. Low-privileged network access is required, and successful triggering stalls background-job processing rather than disclosing or altering data.
Summary
What happened
Infinite loop in GitLab CE/EE allows remote authenticated users to make background jobs unresponsive via CI artifact metadata processing. GitLab identifies CI artifact metadata processing as the affected locus but has not published the loop condition or the metadata operation that fails to terminate. Low-privileged network access is required, and successful triggering stalls background-job processing rather than disclosing or altering data.
The record
- CVE
- CVE-2025-0290
- Published
- Jan 28, 2025
- Updated
- Jan 28, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-835, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 2025CVE publishedPublication date reported by the CVE source.
- Jan 28, 2025Record 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=15.0 <17.6.4
- Affected versionversion=17.7 <17.7.2
- Affected versionversion=17.8 <17.8.0
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