sitaramc/gitolite
CVE History
| CVE | Affected | Published | CVSS v3 | CVSS v2 |
|---|---|---|---|---|
| < 1.4.1 | 9.8 CRITICAL | 7.5 HIGH | ||
gitolite before 1.4.1 does not filter src/ or hooks/ from path names. | ||||
| < 3.6.11 | — | 6.8 MEDIUM | ||
commands/rsync in Gitolite before 3.6.11, if .gitolite.rc enables rsync, mishandles the rsync command line, which allows attackers to have a "bad" impact by triggering use of an option other than -v, -n, -q, or -P. | ||||
| <= 3.5.3 | — | 2.1 LOW | ||
gitolite before commit fa06a34 might allow local users to read arbitrary files in repositories via vectors related to the user umask when running gitolite setup. | ||||
| >= 3.0, <= 3.5.3 | — | 7.5 HIGH | ||
gitolite commit fa06a34 through 3.5.3 might allow attackers to have unspecified impact via vectors involving world-writable permissions when creating (1) ~/.gitolite.rc, (2) ~/.gitolite, or (3) ~/repositories/gitolite-admin.git on fresh installs. | ||||
| < 3.6.9 | — | 5.5 MEDIUM | ||
Gitolite before 3.6.9 does not (in certain configurations involving @all or a regex) properly restrict access to a Git repository that is in the process of being migrated until the full set of migration steps has been completed. This can allow valid users to obtain unintended access. | ||||
| = 3.01, = 3.0, = 3.02, = 3.03, = 3.04 | — | 4.6 MEDIUM | ||
Directory traversal vulnerability in gitolite 3.x before 3.1, when wild card repositories and a pattern matching "../" are enabled, allows remote authenticated users to create arbitrary repositories and possibly perform other actions via a .. (dot dot) in a repository name. | ||||
| = 0.50, = 0.55, = 0.60, = 0.65, = 0.70, = 0.80, = 0.85, = 0.90, = 0.95, = 1.0, = 1.1, = 1.5.1, = 1.5.2, <= 1.5.9, = 1.4, = 1.4.1, = 1.5.5, = 1.5.6, = 1.4.2, = 1.5, = 1.5.7, = 1.5.8, = 1.2, = 1.3, = 1.5.3, = 1.5.4 | — | 6.8 MEDIUM | ||
Directory traversal vulnerability in the Admin Defined Commands (ADC) feature in gitolite before 1.5.9.1 allows remote attackers to execute arbitrary commands via .. (dot dot) sequences in admin-defined commands. | ||||