CVE-2019-10217 · cross-distro fix matrix

CVE-2019-10217: A flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensitive data should be set as such by no_log feature. Some of these fields in GCP modules are not set properly. service_account_contents() which is common class for all gcp modules is not setting no_log to True. Any sensitive data man

Affects 3 Linux releases across 3 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2019-10217 has a known fix. Run the listed command on that distro to remediate.

Debian bullseye

Source: Debian Security Tracker

ansible→ fixed in2.8.6+dfsg-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y ansible
```

Debian bookworm

Source: Debian Security Tracker

ansible→ fixed in2.8.6+dfsg-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y ansible
```

Debian trixie

Source: Debian Security Tracker

ansible→ fixed in2.8.6+dfsg-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y ansible
```

Are YOU affected by CVE-2019-10217?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2019-10217dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. $99 lifetime, 50 founder seats, 30-day refund.

See StackPatch ($99 lifetime)