Directory Traversal Affecting git-bzr package, versions <0:1.8.3.1-14.el7_5


Severity

Recommended
0.0
high
0
10

Based on Oracle Linux security rating.

Threat Intelligence

Exploit Maturity
Mature
EPSS
12.5% (96th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ORACLE7-GITBZR-2525731
  • published10 Apr 2022
  • disclosed30 May 2018

Introduced: 30 May 2018

CVE-2018-11235  (opens in a new tab)
CWE-22  (opens in a new tab)

How to fix?

Upgrade Oracle:7 git-bzr to version 0:1.8.3.1-14.el7_5 or higher.
This issue was patched in ELSA-2018-1957.

NVD Description

Note: Versions mentioned in the description apply only to the upstream git-bzr package and not the git-bzr package as distributed by Oracle. See How to fix? for Oracle:7 relevant fixed versions and status.

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.