LiveActive security incident?Get immediate response
CVE Record

CVE-2018-11235: In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2...

In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur. With a crafted .gitmodules file, a malicious project can execute an arbitrary script on a machine that runs "git clone --recurse-submodules" because submodule "names" are obtained from this file, and then appended to $GIT_DIR/modules, leading to directory traversal with "../" in a name. Finally, post-checkout hooks from a submodule are executed, bypassing the intended design in which hooks are not obtained from a remote server.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A malicious Git repository can run code on a developer or build machine when cloned with recursive submodules using vulnerable Git versions. This matters because source code checkouts often happen on trusted workstations and CI systems with valuable credentials.

Executive priority

Treat this as a high-priority engineering hygiene issue for build and developer infrastructure. It enables code execution through a routine source checkout path, but the provided evidence does not confirm active exploitation.

Technical view

Vulnerable Git versions trust submodule names from .gitmodules and append them under $GIT_DIR/modules. A crafted name can cause directory traversal and lead to execution of a submodule post-checkout hook during recursive clone, bypassing Git's intended protection against remote-supplied hooks.

Likely exposure

Exposure is most likely on developer workstations, CI runners, build servers, and automation that use affected Git versions and clone repositories with recursive submodules, especially from untrusted or externally contributed sources.

Exploitation context

The CVE source bundle includes an Exploit-DB reference, so public exploit material exists. The bundle does not show CISA KEV listing or cited evidence of active exploitation in the wild.

Researcher notes

The key exposure condition is vulnerable Git plus recursive submodule processing of a crafted repository. Focus validation on clone workflows, CI defaults, build containers, and developer tooling rather than internet-facing services alone.

Mitigation direction

  • Upgrade Git to the fixed version for each maintained release branch or vendor package.
  • Prioritize CI runners, build hosts, and developer endpoints that clone external repositories.
  • Avoid recursive submodule cloning from untrusted repositories until Git is patched.
  • Follow Red Hat, Ubuntu, Debian, Gentoo, SUSE, or upstream Git guidance for platform-specific packages.

Validation and detection

  • Inventory Git versions across developer endpoints, CI runners, and build images.
  • Confirm versions are at least 2.13.7, 2.14.4, 2.15.2, 2.16.4, or 2.17.1 as applicable.
  • Identify automation using recursive submodule cloning or submodule initialization.
  • Review source intake workflows for untrusted repositories or external pull-request build jobs.
  • Verify patched package versions against the relevant Linux distribution advisory.
Prepared
Confidence
high
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-11235 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.