Logstash Improper Certificate Validation in TCP output
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Elastic | Logstash | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Elastic | Logstash | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-13629 | 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. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.180% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Logstash Improper Certificate Validation in TCP output | |
| Weaknesses | CWE-295 | |
| References |
| |
| Metrics |
cvssV3_1
|