CVE-2025-37730: Logstash Improper Certificate Validation in TCP output
First published: Tue May 06 2025(Updated: )
Improper certificate validation in Logstash's TCP output could lead to a man-in-the-middle (MitM) attack in “client” mode, as hostname verification in TCP output was not being performed when the ssl_verification_mode => full was set.
Credit: bressers@elastic.co
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Logstash Management API |
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-2025-37730?
CVE-2025-37730 is considered a high severity vulnerability due to the potential for a man-in-the-middle (MitM) attack.
How do I fix CVE-2025-37730?
To fix CVE-2025-37730, ensure that Logstash’s TCP output is configured with proper hostname verification by not setting ssl_verification_mode to full.
What versions of Logstash are affected by CVE-2025-37730?
CVE-2025-37730 affects multiple versions of Elastic Logstash, primarily those configured in 'client' mode with insufficient hostname verification.
What are the risks associated with CVE-2025-37730?
The risks associated with CVE-2025-37730 include exposure to man-in-the-middle attacks that could lead to unauthorized data interception.
Is CVE-2025-37730 being actively exploited?
As of now, there are no confirmed reports of CVE-2025-37730 being actively exploited in the wild.
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/weakness
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/severity
- agent/source
- agent/author
- agent/tags
- agent/event
- vendor/elastic
- canonical/logstash management api