GitLabApplication
CVE-2018-3710
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGitlab Community and Enterprise Editions version 10.3.3 is vulnerable to an Insecure Temporary File in the project import component resulting remote code execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceGitLab Community and Enterprise Edition version 10.3.3 contains an insecure temporary file creation vulnerability in the project import functionality. This vulnerability allows remote code execution, likely through exploitation of predictable or improperly secured temporary file handling during project imports.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitLabApplication
>= 8.9.0, <= 9.5.10>= 10.0.0, <= 10.1.5>= 10.0.0, <= 10.1.15> 10.2.0, <= 10.2.5>= 10.2.0, <= 10.2.5> 10.3.0, <= 10.3.3>= 10.3.0, <= 10.3.3
Debian LinuxOperating system
= 9.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed GitLab versionRun 'gitlab-rake gitlab:env:info' or access the GitLab web interface and navigate to Admin Area > Applications > GitLab version info, or use the API endpoint /api/v4/versionAffected if The displayed version falls within any of these ranges: 8.9.0 to 9.5.10, 10.0.0 to 10.1.15, 10.2.0 to 10.2.5, or 10.3.0 to 10.3.3
-
Verify project import functionality is accessibleCheck if the project import feature is enabled by reviewing GitLab settings at Admin Area > Settings > Repository > Import sources, or attempt to access /projects/new/import via the web interface or APIAffected if Project import sources are enabled and accessible to users (particularly the 'GitLab export' or similar import options)
-
Inspect temporary file handling in import codeOn the GitLab server, examine the project import-related code in the Rails application, specifically looking for FileUtils.tempfile or similar temporary file creation methods in the import handlers (typically under /opt/gitlab/embedded/service/gitlab-rails/lib/api or app/importers/)Affected if Code uses predictable or insecure methods for creating temporary files during project imports without proper sanitization of filenames or secure random generation
If the GitLab version falls within any of the affected ranges AND the project import feature is enabled, the environment is likely vulnerable to CVE-2018-3710.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade GitLab to a patched version beyond 10.3.3 that addresses the insecure temporary file vulnerability in the project import component. Review temporary file handling in custom import implementations.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-3710 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-3710 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data