Service interruption via unbounded approval-rule field
Published Mar 13, 2025 · Updated Mar 14, 2025
Resource exhaustion in affected GitLab EE releases allows attackers to interrupt service via crafted approval-rule API input. The approval-rules API accepts an unbounded field for processing; GitLab has not published the field name or the resource-consuming operation. Exploitation requires user interaction and applies only to certain GitLab EE instances, with service availability as the sole published consequence.
Summary
What happened
Resource exhaustion in affected GitLab EE releases allows attackers to interrupt service via crafted approval-rule API input. The approval-rules API accepts an unbounded field for processing; GitLab has not published the field name or the resource-consuming operation. Exploitation requires user interaction and applies only to certain GitLab EE instances, with service availability as the sole published consequence.
The record
- CVE
- CVE-2025-1257
- Published
- Mar 13, 2025
- Updated
- Mar 14, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 2025CVE publishedPublication date reported by the CVE source.
- Mar 14, 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=12.3 <17.7.7
- Affected versionversion=17.8 <17.8.5
- Affected versionversion=17.9 <17.9.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