# CVE-2023-4237: Platform: ec2_key module prints out the private key directly to the standard output

> The Ansible ec2_key module exposes private keys in standard output, allowing attackers to retrieve sensitive credentials from log files.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Oct 2023
- **Updated:** 25 Feb 2026
- **Also known as:** DEBIAN-CVE-2023-4237, GHSA-ww3m-ffrm-qvqv, PYSEC-2026-1125, UBUNTU-CVE-2023-4237

## What is CVE-2023-4237?

CVE-2023-4237 is a high-severity vulnerability in Red Hat Ansible Automation Platform 2.4 for RHEL 8, published on 4 Oct 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in the Ansible Automation Platform. When creating a new keypair, the ec2_key module prints out the private key directly to the standard output. This flaw allows an attacker to fetch those keys from the log files, compromising the system's confidentiality, integrity, and availability.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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

3 open source packages ship an affected version, including ansible-core. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ansible-core` | PyPI | From 2.8.0 to 2.15.2 | None |
| `ansible-core` | PyPI | From 2.8.0 to 2.15.2 | None |
| `ansible-core` | PyPI | From 2.8.0 to 2.15.2 | None |

Products: Redhat Ansible Automation Platform, Redhat Ansible Collection.

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

Apply the vendor's patch.

## Is CVE-2023-4237 being exploited?

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

## Other vulnerabilities in Red Hat Ansible Automation Platform 2.4 for RHEL 8

- [CVE-2021-4112](https://insights.sbomify.com/CVE-2021-4112/): Privilege escalation in ansible-tower (high 8.8)
- [CVE-2021-3583](https://insights.sbomify.com/CVE-2021-3583/): Improper Input Validation and Command Injection in Ansible (high 7.1)
- [CVE-2025-9907](https://insights.sbomify.com/CVE-2025-9907/): Event-driven-ansible: event stream test mode exposes sensitive headers in aap eda (medium 6.7)
- [CVE-2025-9908](https://insights.sbomify.com/CVE-2025-9908/): Event-driven-ansible: sensitive internal headers disclosure in aap eda event streams (medium 6.7)
- [CVE-2025-9909](https://insights.sbomify.com/CVE-2025-9909/): Aap-gateway: improper path validation in gateway allows credential exfiltration (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4237 is a high-severity vulnerability in Red Hat Ansible Automation Platform 2.4 for RHEL 8, published on 4 Oct 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-4237 in the wild and no public exploit code.

Affected packages and fixed versions:
- ansible-core (PyPI): affected from 2.8.0 up to 2.15.2; no fix listed
- ansible-core (PyPI): affected from 2.8.0 up to 2.15.2; no fix listed
- ansible-core (PyPI): affected from 2.8.0 up to 2.15.2; no fix listed

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-4237/ (Markdown: https://insights.sbomify.com/CVE-2023-4237/index.md)
```

## Sources

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

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