Grafana up to 6.7.3 /var/lib/grafana Credentials cleartext storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Grafana up to 6.7.3 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /var/lib/grafana. Performing a manipulation results in cleartext storage (Credentials). This vulnerability is known as CVE-2020-12458. Attacking locally is a requirement. No exploit is available.
Details
A vulnerability, which was classified as problematic, was found in Grafana up to 6.7.3. This affects an unknown part of the file /var/lib/grafana. The manipulation with an unknown input leads to a cleartext storage vulnerability (Credentials). CWE is classifying the issue as CWE-312. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. This is going to have an impact on confidentiality. The summary by CVE is:
An information-disclosure flaw was found in Grafana through 6.7.3. The database directory /var/lib/grafana and database file /var/lib/grafana/grafana.db are world readable. This can result in exposure of sensitive information (e.g., cleartext or encrypted datasource passwords).
The weakness was published 04/29/2020. This vulnerability is uniquely identified as CVE-2020-12458 since 04/29/2020. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1555 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 236664 (Alibaba Cloud Linux 3 : 0073: grafana (ALINUX3-SA-2021:0073)), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Tenable (236664). Similar entry is available at VDB-154606. 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: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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
Name: CredentialsClass: Cleartext storage / Credentials
CWE: CWE-312 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: 236664
Nessus Name: Alibaba Cloud Linux 3 : 0073: grafana (ALINUX3-SA-2021:0073)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/29/2020 🔍04/29/2020 🔍
04/30/2020 🔍
05/18/2025 🔍
Sources
Advisory: 8283Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-12458 (🔍)
GCVE (CVE): GCVE-0-2020-12458
GCVE (VulDB): GCVE-100-154605
See also: 🔍
Entry
Created: 04/30/2020 09:36Updated: 05/18/2025 19:33
Changes: 04/30/2020 09:36 (36), 04/30/2020 09:41 (17), 10/14/2020 13:59 (1), 06/04/2024 14:29 (19), 05/18/2025 19:33 (3)
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.