gitolite up to 3.6.10 rsync .gitolite.rc input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in gitolite up to 3.6.10. This affects an unknown function of the file .gitolite.rc of the component rsync Handler. The manipulation leads to input validation. This vulnerability is referenced as CVE-2018-20683. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.
Details
A vulnerability was found in gitolite up to 3.6.10. It has been rated as critical. This issue affects some unknown functionality of the file .gitolite.rc of the component rsync Handler. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The bug was discovered 01/09/2019. The weakness was published 01/10/2019 (Website). The advisory is shared at bugs.debian.org. The identification of this vulnerability is CVE-2018-20683 since 01/09/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 121283 (openSUSE Security Update : gitolite (openSUSE-2019-54)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l.
Upgrading to version 3.6.11 eliminates this vulnerability. A possible mitigation has been published 3 months after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (121283). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.1VulDB Meta Temp Score: 7.9
VulDB Base Score: 8.1
VulDB Temp Score: 7.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 121283
Nessus Name: openSUSE Security Update : gitolite (openSUSE-2019-54)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: gitolite 3.6.11
Patch: github.com
Timeline
01/09/2019 🔍01/09/2019 🔍
01/09/2019 🔍
01/10/2019 🔍
01/11/2019 🔍
01/22/2019 🔍
03/23/2019 🔍
06/26/2023 🔍
Sources
Advisory: 5df2b817255ee919991da6c310239e08c8fcc1aeStatus: Not defined
CVE: CVE-2018-20683 (🔍)
GCVE (CVE): GCVE-0-2018-20683
GCVE (VulDB): GCVE-100-129005
Entry
Created: 01/11/2019 08:09Updated: 06/26/2023 09:22
Changes: 01/11/2019 08:09 (69), 04/28/2020 14:53 (2), 06/26/2023 09:22 (5)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.