GitLab Community Edition/Enterprise Edition up to 12.1.4 hard-coded credentials
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
8.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in GitLab Community Edition and Enterprise Edition up to 12.1.4. Affected is an unknown function. The manipulation leads to hard-coded credentials. This vulnerability is traded as CVE-2019-14943. It is possible to launch the attack remotely. There is no exploit available. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 12.1.4 (Bug Tracking Software). It has been rated as critical. This issue affects an unknown code. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. Using CWE to declare the problem leads to CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in GitLab Community and Enterprise Edition 12.0 through 12.1.4. It uses Hard-coded Credentials.
The weakness was disclosed 08/29/2019 (Website). It is possible to read the advisory at about.gitlab.com. The identification of this vulnerability is CVE-2019-14943 since 08/11/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1110.001 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/11/2019 🔍08/29/2019 🔍
08/29/2019 🔍
12/07/2023 🔍
Sources
Vendor: gitlab.comAdvisory: 4530
Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-14943 (🔍)
GCVE (CVE): GCVE-0-2019-14943
GCVE (VulDB): GCVE-100-141047
Entry
Created: 08/29/2019 07:55 PMUpdated: 12/07/2023 03:05 PM
Changes: 08/29/2019 07:55 PM (55), 08/09/2020 11:37 AM (1), 12/07/2023 03:05 PM (3)
Complete: 🔍
Cache ID: 18:315:40
No comments yet. Languages: en.
Please log in to comment.