CVE-2022-3697

A flaw was found in Ansible in the amazon.aws collection when using the tower_callback parameter from the amazon.aws.ec2_instance module. This flaw allows an attacker to take advantage of this issue as the module is handling the parameter insecurely, leading to the password leaking in the logs.

Published: 2022-10-28 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-3697 is rated Moderate Risk (47.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.71%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-3697

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.19% 0.71% +0.52%
2 2026-03-25 0.13% 0.19% +0.06%
3 2025-11-21 — 0.13% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-3697

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2022-3697

GitHub Security Advisory for CVE-2022-3697

OS Trackers for CVE-2022-3697

vendor priority summary link
debian not yet assigned CVE-2022-3697 not yet assigned priority: Debian including 1 source packages (ansible), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-3697
redhat medium — https://access.redhat.com/security/cve/CVE-2022-3697
suse medium CVE-2022-3697 severity moderate: SUSE including 3 source package names (ansible, ansible-doc, ansible1), 13 product×package rows across 9 product lines (HPE Helion OpenStack 8, SUSE Linux Enterprise Server 11 SP3 for Teradata, … (9 product lines)): Known Not Affected 13. https://www.suse.com/security/cve/CVE-2022-3697/
ubuntu medium CVE-2022-3697 medium priority: Ubuntu including 2 source packages (ansible, ansible-core), 26 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 7, not-affected 7, DNE 4, needs-triage 4, released 4. https://ubuntu.com/security/CVE-2022-3697

Affected software / configurations for CVE-2022-3697

Vendor Product Version Raw CPE
redhat ansible >= 2.5.0, < 2.10.0 cpe:2.3:a:redhat:ansible:*:*:*:*:*:*:*:*
redhat ansible_collection < 2.0.0 cpe:2.3:a:redhat:ansible_collection:*:*:*:*:*:community_aws:*:*
redhat ansible_collection >= 2.1.0, < 5.1.0 cpe:2.3:a:redhat:ansible_collection:*:*:*:*:*:aws:*:*

References for CVE-2022-3697

cvelogic Threat Intelligence