CVE-2018-16976: Race Condition
First published: Wed Sep 12 2018(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Gitolite | <3.6.9 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-16976?
CVE-2018-16976 has a medium severity level due to its potential to allow unauthorized access to Git repositories.
How do I fix CVE-2018-16976?
To fix CVE-2018-16976, upgrade to Gitolite version 3.6.9 or later.
Who is affected by CVE-2018-16976?
Users of Gitolite versions prior to 3.6.9 that either use @all or regex configurations are affected by CVE-2018-16976.
What kind of access does CVE-2018-16976 allow?
CVE-2018-16976 may allow valid users to gain unintended access to a Git repository during migration processes.
Is CVE-2018-16976 exploitable in all configurations?
No, CVE-2018-16976 is only exploitable in certain configurations involving @all or regex.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/severity
- agent/weakness
- agent/remedy
- agent/references
- agent/last-modified-date
- agent/softwarecombine
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitolite
- canonical/gitolite