# CVE-2023-31413: Information disclosure in Filebeat

> Attackers can read sensitive authorization headers from logs if debug logging is enabled in Elastic Filebeat.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 May 2023
- **Updated:** 29 Jan 2025
- **Also known as:** GHSA-j8h4-w7cf-hch5

## What is CVE-2023-31413?

CVE-2023-31413 is a medium-severity vulnerability in Elastic Filebeat, published on 4 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Filebeat versions through 7.17.9 and 8.6.2 have a flaw in httpjson input that allows the http request Authorization or Proxy-Authorization header contents to be leaked in the logs when debug logging is enabled.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-31413?

It affects 1 product.


Products: Elastic Filebeat.

## How do I fix CVE-2023-31413?

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

## Is CVE-2023-31413 being exploited?

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

## Other vulnerabilities in Elastic Filebeat

- [CVE-2026-78588](https://insights.sbomify.com/CVE-2026-78588/): Allocation of Resources Without Limits or Throttling in Filebeat Leading to Denial of Service (medium 6.5)
- [CVE-2025-68383](https://insights.sbomify.com/CVE-2025-68383/): Filebeat Improper Validation of Specified Index, Position, or Offset in Input (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31413 and fix it if it is affected.

What it is: CVE-2023-31413 is a medium-severity vulnerability in Elastic Filebeat, published on 4 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-31413 in the wild and no public exploit code.

Affected product: Elastic Filebeat. 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-2023-31413/ (Markdown: https://insights.sbomify.com/CVE-2023-31413/index.md)
```

## Sources

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

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