# CVE-2023-4586: Hotrod-client: hot rod client does not enable hostname validation when using tls that lead to a mitm attack

> The Hot Rod client fails to validate hostnames during TLS connections, allowing attackers to perform man-in-the-middle attacks to intercept or modify data.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2023
- **Updated:** 20 Nov 2025

## What is CVE-2023-4586?

CVE-2023-4586 is a high-severity vulnerability in Red Hat Data Grid 8.4.6, published on 4 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in the Hot Rod client. This security issue occurs as the Hot Rod client does not enable hostname validation when using TLS, possibly resulting in a man-in-the-middle (MITM) attack.

Weakness: CWE-295 (Improper Certificate Validation), CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Infinispan Hot Rod, Redhat Data Grid.

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

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

## Is CVE-2023-4586 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4586 is a high-severity vulnerability in Red Hat Data Grid 8.4.6, published on 4 Oct 2023. 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-2023-4586 in the wild and no public exploit code.

Affected product: Red Hat Data Grid 8.4.6. 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-4586/ (Markdown: https://insights.sbomify.com/CVE-2023-4586/index.md)
```

## Sources

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

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