CVE-2018-3827
CVE-2018-3827 is a high-severity vulnerability in Elastic Azure Repository with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-532.
Key facts
- Severity: High (CVSS 3.x base score 8.1)
- CVSS v2: 4.3
- EPSS exploit prediction: 1% (59th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-532
- Affected product: Elastic Azure Repository
- Published:
- Last modified:
Description
A sensitive data disclosure flaw was found in the Elasticsearch repository-azure (formerly elasticsearch-cloud-azure) plugin. When the repository-azure plugin is set to log at TRACE level Azure credentials can be inadvertently logged.
Frequently asked questions
- What is CVE-2018-3827?
- A sensitive data disclosure flaw was found in the Elasticsearch repository-azure (formerly elasticsearch-cloud-azure) plugin. When the repository-azure plugin is set to log at TRACE level Azure credentials can be inadvertently logged.
- How severe is CVE-2018-3827?
- CVE-2018-3827 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2018-3827 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (59th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2018-3827?
- CVE-2018-3827 primarily affects Elastic Azure Repository. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2018-3827?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2018-3827 published?
- CVE-2018-3827 was published on 2018-09-19 and last updated on 2026-06-17.
References
- https://discuss.elastic.co/t/elastic-stack-6-3-0-and-5-6-10-security-update/135777
- https://www.elastic.co/community/security
Affected products (3)
- cpe:2.3:a:elastic:azure_repository:*:*:*:*:*:azure:*:*
- cpe:2.3:a:elastic:azure_repository:6.0.0:beta1:*:*:*:azure:*:*
- cpe:2.3:a:elastic:azure_repository:6.0.0:beta2:*:*:*:azure:*:*
Other CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities
- CVE-2022-36407 — Critical (CVSS 9.9): Insertion of Sensitive Information into Log File vulnerability in Hitachi Virtual Storage Platform, Hitachi Virtual…
- CVE-2023-40029 — Critical (CVSS 9.9): Argo CD is a declarative continuous deployment for Kubernetes. Argo CD Cluster secrets might be managed declaratively…
- CVE-2021-32724 — Critical (CVSS 9.9): check-spelling is a github action which provides CI spell checking. In affected versions and for a repository with the…
- CVE-2026-49200 — Critical (CVSS 9.8): The acer_cgi.log file in the device firmware is accessible without authentication via the web interface. This file…
- CVE-2026-22778 — Critical (CVSS 9.8): vLLM is an inference and serving engine for large language models (LLMs). From 0.8.3 to before 0.14.1, when an invalid…
- CVE-2025-11008 — Critical (CVSS 9.8): The CE21 Suite plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and…
Browse all CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities →