CVE-2018-3827
First published: Wed Sep 19 2018(Updated: )
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.
Credit: bressers@elastic.co
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Elastic Azure Repository | >=6.0.1<=6.2.4 | |
| Elastic Azure Repository | =6.0.0-beta1 | |
| Elastic Azure Repository | =6.0.0-beta2 |
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-3827?
The severity of CVE-2018-3827 is classified as a moderate vulnerability.
How do I fix CVE-2018-3827?
To fix CVE-2018-3827, upgrade the Elasticsearch repository-azure plugin to a version that is not affected by this issue.
Which versions are affected by CVE-2018-3827?
CVE-2018-3827 affects versions 6.0.1 to 6.2.4 of the Elasticsearch repository-azure plugin.
What type of vulnerability is CVE-2018-3827?
CVE-2018-3827 is a sensitive data disclosure vulnerability related to Azure credentials.
Can I continue using affected versions of the repository-azure plugin with CVE-2018-3827?
Using affected versions of the repository-azure plugin is not recommended due to the risk of sensitive data exposure.
- collector/nvd-index
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/references
- agent/description
- agent/type
- agent/first-publish-date
- agent/author
- agent/event
- agent/tags
- agent/source
- vendor/elastic
- canonical/elastic azure repository
- version/elastic azure repository/6.0.1
- version/elastic azure repository/6.2.4
- version/elastic azure repository/6.0.0-beta1
- version/elastic azure repository/6.0.0-beta2