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.
The MITRE CVE dictionary describes this issue as:
Find out more about CVE-2018-11235 from the MITRE CVE dictionary dictionary and NIST NVD.
This issue did not affect the versions of git as shipped with Red Hat Enterprise Linux 6 as they did not include the vulnerable code.
If using OCP 3.6 make sure atomic-openshift-3.6.173.0.128-1.git.0.8da0828.el7 or later is installed on the master.
| CVSS3 Base Score | 8.8 |
|---|---|
| CVSS3 Base Metrics | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| Attack Vector | Network |
| Attack Complexity | Low |
| Privileges Required | None |
| User Interaction | Required |
| Scope | Unchanged |
| Confidentiality | High |
| Integrity Impact | High |
| Availability Impact | High |
| Platform | Errata | Release Date |
|---|---|---|
| Red Hat Enterprise Linux 7 (git) | RHSA-2018:1957 | 2018-06-21 |
| Red Hat Software Collections for Red Hat Enterprise Linux 7 (rh-git29-git) | RHSA-2018:2147 | 2018-07-10 |
| Red Hat Software Collections for Red Hat Enterprise Linux 6 (rh-git29-git) | RHSA-2018:2147 | 2018-07-10 |
| Platform | Package | State |
|---|---|---|
| Red Hat OpenShift Enterprise 3.2 | source-to-image | Will not fix |
| Red Hat OpenShift Enterprise 3.1 | source-to-image | Will not fix |
| Red Hat OpenShift Enterprise 3.0 | source-to-image | Will not fix |
| Red Hat OpenShift Enterprise 3 | atomic-openshift | Not affected |
| Red Hat OpenShift Container Platform 3.9 | source-to-image | Not affected |
| Red Hat OpenShift Container Platform 3.7 | source-to-image | Not affected |
| Red Hat OpenShift Container Platform 3.6 | source-to-image | Not affected |
| Red Hat OpenShift Container Platform 3.5 | source-to-image | Will not fix |
| Red Hat OpenShift Container Platform 3.4 | source-to-image | Will not fix |
| Red Hat OpenShift Container Platform 3.3 | source-to-image | Will not fix |
| Red Hat OpenShift Container Platform 3.10 | source-to-image | Not affected |
| Red Hat Mobile Application Platform On-Premise 4 | fh-scm | Not affected |
| Red Hat JBoss Fuse Service Works 6 | jgit | Not affected |
| Red Hat JBoss Fuse 7 | camel | Not affected |
| Red Hat JBoss Fuse 6 | camel | Not affected |
| Red Hat JBoss Data Virtualization 6 | jgit | Not affected |
| Red Hat JBoss BRMS 6 | jgit | Not affected |
| Red Hat JBoss A-MQ 6 | jgit | Not affected |
| Red Hat Enterprise Linux 6 | git | Not affected |
Don't create OCP source-to-image applications from source code repositories hosted by untrusted parties. Github is blocking users from pushing repositories with malicious submodules so it's less likely you can pull a malicious repository from there which triggers this vulnerability.
Vulmon