CVE-2024-0690

Sensitive task-output disclosure via late no_log defaulting

Published Feb 6, 2024 · Updated Nov 6, 2025

Information disclosure in Red Hat Ansible Core allows local users to read sensitive task output despite ANSIBLE_NO_LOG. The Base.no_log field lacked the C.DEFAULT_NO_LOG initializer, so task and loop output was rendered before PlayContext applied the global default. Exploitation requires low-privileged local access and user interaction with an affected runtime configured for global no-log output; disclosed data can include decrypted secrets.

CVSS severity5.0
Medium
EPSS probability0.30%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in Red Hat Ansible Core allows local users to read sensitive task output despite ANSIBLE_NO_LOG. The Base.no_log field lacked the C.DEFAULT_NO_LOG initializer, so task and loop output was rendered before PlayContext applied the global default. Exploitation requires low-privileged local access and user interaction with an affected runtime configured for global no-log output; disclosed data can include decrypted secrets.

The record

CVE
CVE-2024-0690
Published
Feb 6, 2024
Updated
Nov 6, 2025
Vendor
389 Directory Server
Product
Red Hat Ansible Core
Classifications
CWE-116, CWE-117
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 6, 2024CVE publishedPublication date reported by the CVE source.
  2. Nov 6, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.14.0 <2.14.4
  2. Affected versionversion=2.15.0 <2.15.9
  3. Affected versionversion=2.16.0 <2.16.3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

389 Directory Server · Red Hat Ansible Coreversion=2.14.0 <2.14.4; version=2.15.0 <2.15.9; version=2.16.0 <2.16.3
Red Hat · Red Hat Enterprise Linux 8Affected versions are unavailable in this record.
Red Hat · Red Hat Ansible Automation PlatformAffected versions are unavailable in this record.
Red Hat · Red Hat Enterprise Linux 9Affected versions are unavailable in this record.

Published CVSS scores

5.0Red Hat, Inc.CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-116Improper Encoding or Escaping of Output
CWE-117Improper Output Neutralization for Logs

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo