CVE-2013-4451: gitolite commit fa06a34 through 3.5.3 might allow attackers to have unspecified impact via vectors involving w

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2013-4451 is a critical-severity flaw (CVSS 9.8) affecting gitolite. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.1% (top 12%)
CISA exploited list	No
Weakness	CWE-264
Published	2018-09-21
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: gitolite

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-09-21 17:29 UTCPublished CVE record published
2026-06-16 23:57 UTCUpdated Record last modified

gitolite gitolite UPGRADE

Affected: >= 3.0 and <= 3.5.3

Fixed in: newer than 3.5.3

Safe to downgrade to: a release before 3.0

1. Check installed version

apt-cache policy gitolite || rpm -q gitolite || gitolite --version

2. UPGRADE to newer than 3.5.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gitolite

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gitolite

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.0 (Debian / Ubuntu)

apt-cache madison gitolite sudo apt install gitolite=<VERSION_BEFORE_3.0> sudo apt-mark hold gitolite

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list gitolite sudo dnf downgrade gitolite-<VERSION_BEFORE_3.0> sudo dnf versionlock add gitolite

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2013-4451?

gitolite: upgrade to newer than 3.5.3. Exact commands for each OS are on this page.

Is CVE-2013-4451 being exploited?

CVE-2013-4451 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2013-4451 affect?

CVE-2013-4451 affects gitolite. Severity is critical (CVSS 9.8). 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 ins

How urgent is CVE-2013-4451?

Priority 61/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Git vulnerabilities

Related CVEs

CVE-2018-20683 HIGH 8.1 UPGRADE commands/rsync in Gitolite before 3.6.11, if .gitolite.rc enables rsync, mishandles the rsync command line, wh
CVE-2018-16976 HIGH 8.1 UPGRADE Gitolite before 3.6.9 does not (in certain configurations involving @all or a regex) properly restrict access
CVE-2013-7203 MEDIUM 5.5 UPGRADE gitolite before commit fa06a34 might allow local users to read arbitrary files in repositories via vectors rel
CVE-2010-2447 CRITICAL 9.8 UPGRADE gitolite before 1.4.1 does not filter src/ or hooks/ from path names.

References

← Back to latest CVEs