Cyber Resilience

CVE-2023-5764

Redhat Ansible ≤ 2.14.12

Published
12 December 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 7.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0054 42th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2023-5764 is a high-severity Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336) vulnerability in Redhat Ansible. Its CVSS base score is 7.1 (High).

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

EU & UK References

Vulnerability Data

A template injection flaw was found in Ansible where a user's controller internal templating operations may remove the unsafe designation from template data. This issue could allow an attacker to use a specially crafted file to introduce templating injection when…

more

supplying templating data.

CWE(s)
CWE-1336NVD-CWE-Other

Related Threats

CVEs Like This One

CVE-2024-0690Same product: Fedoraproject Fedora
CVE-2023-40549Same product: Fedoraproject Fedora
CVE-2023-2700Same product: Fedoraproject Fedora
CVE-2023-40550Same product: Fedoraproject Fedora
CVE-2023-40546Same product: Fedoraproject Fedora
CVE-2023-40551Same 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

Affected Assets

redhat
ansible
2.16.0 · ≤ 2.14.12 · 2.15.0 — 2.15.7
fedoraproject
extra packages for enterprise linux
8.0
fedoraproject
fedora
38, 39
redhat
ansible automation platform
2.4
redhat
ansible developer
1.1
redhat
ansible inside
1.2

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.3.2
  • V1.3.7
  • V1.3.10

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 directly require proper input neutralization in template engines to prevent injection.

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.29 Security testing in development and acceptance mostly match
detects

Security testing can detect template-injection flaws but does not itself implement neutralization controls.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and sanitization that directly prevents template-injection weaknesses.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for neutralizing special elements in template engines.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of unsafe template processing but do not prescribe specific neutralization techniques.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper escaping or sandboxing of template directives, directly mitigating CWE-1336.

References