Cyber Resilience

CVE-2024-0690

Redhat Ansible ≤ 2.14.4

Published
06 February 2024
Modified
04 November 2025
Patch / advisory
View advisory
CVSS Score v3.1 5.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
EPSS Score 0.0030 23th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2024-0690 is a medium-severity Improper Output Neutralization for Logs (CWE-117) vulnerability in Redhat Enterprise Linux. Its CVSS base score is 5.0 (Medium).

Operationally, ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A05:2025 InjectionA09:2025 Security Logging and Alerting Failures

EU & UK References

Vulnerability Data

An information disclosure flaw was found in ansible-core due to a failure to respect the ANSIBLE_NO_LOG configuration in some scenarios. Information is still included in the output in certain tasks, such as loop items. Depending on the task, this issue…

more

may include sensitive information, such as decrypted secret values.

CWE(s)
CWE-117CWE-116

Related Threats

CVEs Like This One

CVE-2023-5764Same product: Fedoraproject Fedora
CVE-2025-9908Same product: Redhat Ansible Automation Platform
CVE-2023-4380Same product: Redhat Ansible Automation Platform
CVE-2025-9909Same product: Redhat Ansible Automation Platform
CVE-2025-9907Same product: Redhat Ansible Automation Platform
CVE-2024-10033Same product: Redhat Ansible Automation Platform
CVE-2023-40549Same product: Fedoraproject Fedora
CVE-2023-2700Same product: Fedoraproject Fedora
CVE-2023-40550Same product: Fedoraproject Fedora
CVE-2023-40546Same product: Fedoraproject Fedora

Affected Assets

redhat
ansible
≤ 2.14.4 · 2.15.0 — 2.15.9 · 2.16.0 — 2.16.3
redhat
enterprise linux
8.0, 9.0
redhat
ansible automation platform
2.4
redhat
ansible developer
1.1
redhat
ansible inside
1.2
fedoraproject
fedora
38, 39

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.2.1
  • V1.2.3

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SI-15 Information Output Filtering
addresses: CWE-116 CWE-117

Validating that output matches expected content directly mitigates failures to properly encode or escape data for its destination context.

AU-1 Policy and Procedures
addresses: CWE-117

Policy and procedures require sanitization and neutralization when generating audit logs to avoid injection issues.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices and coding standards directly require output sanitization for logs.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding mostly match
prevents

Secure coding standards explicitly require correct output encoding and escaping to preserve message structure.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect log injection flaws but does not prevent them at the source.

A.8.15 Logging partial match
degrades

Logging control directly requires proper log generation and handling, which mitigates improper output neutralization.

A.8.16 Monitoring activities partial match
detects

Monitoring activities rely on trustworthy logs but do not ensure log message integrity.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC includes coding standards that reduce log-related weaknesses but does not specifically address logging.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit rules for safe output handling and encoding.

References