# CVE-2024-1657: Platform: insecure websocket used when interacting with eda server

> An attacker on the local network can intercept insecure WebSocket traffic to read and modify Ansible rulebook data, compromising system confidentiality and integrity.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Apr 2024
- **Updated:** 25 Feb 2026
- **Also known as:** GHSA-r8mm-5386-h387

## What is CVE-2024-1657?

CVE-2024-1657 is a high-severity vulnerability in Red Hat Ansible Automation Platform 2.4 for RHEL 8, published on 25 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the ansible automation platform. An insecure WebSocket connection was being used in installation from the Ansible rulebook EDA server. An attacker that has access to any machine in the CIDR block could download all rulebook data from the WebSocket, resulting in loss of confidentiality and integrity of the system.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2024-1657?


## How do I fix CVE-2024-1657?

Apply the vendor's patch.

## Is CVE-2024-1657 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1657 and fix it if it is affected.

What it is: CVE-2024-1657 is a high-severity vulnerability in Red Hat Ansible Automation Platform 2.4 for RHEL 8, published on 25 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1657 in the wild and no public exploit code.

Affected product: Red Hat Ansible Automation Platform 2.4 for RHEL 8. 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-2024-1657/ (Markdown: https://insights.sbomify.com/CVE-2024-1657/index.md)
```

## Sources

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

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