CVE-2018-14364
Public exploit available. Not confirmed exploited in the wild yet. Fixed in 10.7.7.
What to do
Find your product and version, then upgrade to the build on the right.
- GitlabAffected: < 10.7.7Upgrade to: 10.7.7Stated by: NVD
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check your GitLab version (Admin Area → Help, or run
gitlab-rake gitlab:env:info) and confirm whether it's older than 10.7.7, 10.8.6, or 11.0.4. - If the project import feature is enabled and your GitLab is internet-reachable, treat this as urgent.
- Upgrade to GitLab 10.7.7, 10.8.6, or 11.0.4 (or later) following GitLab's official upgrade path for your version.
- If you cannot upgrade immediately, disable the project import feature as a temporary measure.
- After upgrading, review server and application logs for signs of unexpected file writes during the vulnerable period.
What it is
From the CVE record
GitLab Community and Enterprise Edition before 10.7.7, 10.8.x before 10.8.6, and 11.x before 11.0.4 allows Directory Traversal with write access and resultant remote code execution via the GitLab projects import component.
In plain language
Written by AI from the recordA serious flaw in older GitLab versions lets an outside attacker take full control of your server without even logging in — if you run a vulnerable version (before 10.7.7, 10.8.6, or 11.0.4), you should act.
Unauthenticated path traversal in GitLab's project import feature allows arbitrary file write outside the upload directory, leading to remote code execution on the server.
If you're affected
- Full server takeover
- Source code and secrets exposure
- Ransomware risk
- Operational disruption
- Customer data exposure
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
2 sources with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
48% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
The patch came 471 days before any public exploit.
- EPSS band changehigh → moderateepss band change
- EPSS band changemoderate → high
- EPSS band changemoderate → highepss band change
- EPSS band changehigh → moderateepss band change
- EPSS band changemoderate → highepss band change
- EPSS band changehigh → moderateepss band change
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.0 vector
Open in the CVSS calculatorCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Scored 9.8 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Gitlab, not every advisory. This one: public exploit.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI