Unauthenticated service interruption via CI parser exhaustion
Published Mar 10, 2020 · Updated Aug 4, 2024
Resource exhaustion in the GitLab CI parser in GitLab Community and Enterprise Edition before 12.0.3 allows remote attackers to interrupt service. GitLab has not published which parser is affected or the specific operation that consumes resources while processing attacker-controlled CI input. Network access without authentication is sufficient, and successful exploitation exhausts resources and interrupts GitLab availability without a reported confidentiality or integrity impact.
Summary
What happened
Resource exhaustion in the GitLab CI parser in GitLab Community and Enterprise Edition before 12.0.3 allows remote attackers to interrupt service. GitLab has not published which parser is affected or the specific operation that consumes resources while processing attacker-controlled CI input. Network access without authentication is sufficient, and successful exploitation exhausts resources and interrupts GitLab availability without a reported confidentiality or integrity impact.
The record
- CVE
- CVE-2019-13003
- Published
- Mar 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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