Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-3697: A flaw was found in Ansible in the amazon.aws collection when using the tower_callback parameter from the amaz

51
This month
HIGH 7.5REMOTEWATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2022-3697 is a high-severity flaw (CVSS 7.5) affecting ansible, ansible collection, ansible collection. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.9% (top 40%)
CISA exploited listNo
WeaknessCWE-233
Published2022-10-28
Last modified2026-06-17
Publisher (CNA): Red Hat, Inc. · Vendor: redhat

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

redhat ansible UPGRADE
Affected: >= 2.5.0 and < 2.10.0
Fixed in: 2.10.0
Safe to downgrade to: a release before 2.5.0
1. Check installed version
apt-cache policy ansible || rpm -q ansible || ansible --version
2. UPGRADE to 2.10.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade ansible
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade ansible
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.5.0 (Debian / Ubuntu)
apt-cache madison ansible sudo apt install ansible=<VERSION_BEFORE_2.5.0> sudo apt-mark hold ansible
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list ansible sudo dnf downgrade ansible-<VERSION_BEFORE_2.5.0> sudo dnf versionlock add ansible
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
redhat ansible collection UPGRADE
Affected: < 2.0.0
Fixed in: 2.0.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy ansible-collection || rpm -q ansible-collection || ansible-collection --version
2. UPGRADE to 2.0.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade ansible-collection
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade ansible-collection
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
redhat ansible collection UPGRADE
Affected: >= 2.1.0 and < 5.1.0
Fixed in: 5.1.0
Safe to downgrade to: a release before 2.1.0
1. Check installed version
apt-cache policy ansible-collection || rpm -q ansible-collection || ansible-collection --version
2. UPGRADE to 5.1.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade ansible-collection
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade ansible-collection
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.1.0 (Debian / Ubuntu)
apt-cache madison ansible-collection sudo apt install ansible-collection=<VERSION_BEFORE_2.1.0> sudo apt-mark hold ansible-collection
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list ansible-collection sudo dnf downgrade ansible-collection-<VERSION_BEFORE_2.1.0> sudo dnf versionlock add ansible-collection
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-3697?

ansible: upgrade to 2.10.0; ansible collection: upgrade to 2.0.0; ansible collection: upgrade to 5.1.0. Exact commands for each OS are on this page.

Is CVE-2022-3697 being exploited?

CVE-2022-3697 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-3697 affect?

CVE-2022-3697 affects ansible, ansible collection, ansible collection. Severity is high (CVSS 7.5). 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 i

How urgent is CVE-2022-3697?

Priority 51/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Ansible vulnerabilities · AWS vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.