# CVE-2018-3827: Information disclosure in Elasticsearch

> Azure credentials may be exposed in logs when the Elasticsearch repository-azure plugin is configured to log at TRACE level.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xc6w-7c69-3cf8

## What is CVE-2018-3827?

CVE-2018-3827 is a high-severity vulnerability in Elasticsearch, published on 19 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2018-3827?

It affects 1 product.


Products: Elastic Azure Repository.

## How do I fix CVE-2018-3827?

No fix has been published for CVE-2018-3827 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-3827 being exploited?

There is no known exploitation of CVE-2018-3827 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3827 and fix it if it is affected.

What it is: CVE-2018-3827 is a high-severity vulnerability in Elasticsearch, published on 19 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3827 in the wild and no public exploit code.

Affected product: Elasticsearch. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-3827/ (Markdown: https://insights.sbomify.com/CVE-2018-3827/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-3827
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-3827
- OSV: https://osv.dev/vulnerability/CVE-2018-3827

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-3827/
Summaries are generated and may contain mistakes; the official description above is the record.