# CVE-2013-4451: Misconfiguration in n/a

> Attackers can exploit world-writable permissions on fresh Gitolite installs to modify configuration or repositories, leading to privilege escalation.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p485-m5mg-88jg

## What is CVE-2013-4451?

CVE-2013-4451 is a critical vulnerability in n/a, published on 21 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-264

## Which versions are affected by CVE-2013-4451?

It affects 1 product.


Products: Gitolite Gitolite.

## How do I fix CVE-2013-4451?

No fix has been published for CVE-2013-4451 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-4451 being exploited?

There is no known exploitation of CVE-2013-4451 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2010-2447](https://insights.sbomify.com/CVE-2010-2447/): Path traversal in n/a (critical 9.8)
- [CVE-2018-20683](https://insights.sbomify.com/CVE-2018-20683/): Command injection in n/a (high 8.1)
- [CVE-2018-16976](https://insights.sbomify.com/CVE-2018-16976/): Race condition in n/a (high 8.1)
- [CVE-2011-1572](https://insights.sbomify.com/CVE-2011-1572/): Path traversal in n/a (medium 6.8)
- [CVE-2013-7203](https://insights.sbomify.com/CVE-2013-7203/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4451 and fix it if it is affected.

What it is: CVE-2013-4451 is a critical vulnerability in n/a, published on 21 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4451 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-4451/ (Markdown: https://insights.sbomify.com/CVE-2013-4451/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4451
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4451
- OSV: https://osv.dev/vulnerability/CVE-2013-4451

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-4451/
Summaries are generated and may contain mistakes; the official description above is the record.