| Name | CVE-2020-1733 |
| Description | A race condition flaw was found in Ansible Engine 2.7.17 and prior, 2.8.9 and prior, 2.9.6 and prior when running a playbook with an unprivileged become user. When Ansible needs to run a module with become user, the temporary directory is created in /var/tmp. This directory is created with "umask 77 && mkdir -p <dir>"; this operation does not fail if the directory already exists and is owned by another user. An attacker could take advantage to gain control of the become user as the target directory can be retrieved by iterating '/proc/<pid>/cmdline'. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| References | DLA-2202-1, DSA-4950-1 |
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|---|---|---|
| ansible (PTS) | jessie, jessie (lts) | 1.7.2+dfsg-2+deb8u3 | fixed |
| stretch (security), stretch (lts), stretch | 2.2.1.0-2+deb9u3 | vulnerable | |
| buster (security), buster, buster (lts) | 2.7.7+dfsg-1+deb10u2 | fixed | |
| bullseye | 2.10.7+merged+base+2.10.17+dfsg-0+deb11u1 | fixed | |
| bullseye (security) | 2.10.7+merged+base+2.10.17+dfsg-0+deb11u2 | fixed | |
| bookworm | 7.7.0+dfsg-3+deb12u1 | fixed | |
| sid, trixie | 11.1.0+dfsg-1 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|---|---|---|---|---|---|
| ansible | source | jessie | 1.7.2+dfsg-2+deb8u3 | DLA-2202-1 | ||
| ansible | source | stretch | (unfixed) | end-of-life | ||
| ansible | source | buster | 2.7.7+dfsg-1+deb10u1 | DSA-4950-1 | ||
| ansible | source | (unstable) | 2.9.7+dfsg-1 |
[stretch] - ansible <end-of-life> (EOL'd for stretch)
https://bugzilla.redhat.com/show_bug.cgi?id=1801735
https://github.com/ansible/ansible/issues/67791
https://github.com/ansible/ansible/pull/68921
https://github.com/ansible/ansible/commit/8077d8e40148fe77e2393caa5f2b2ea855149d63
When applying the fix for CVE-2020-1733 make sure to apply complete fix to
not open up CVE-2020-10744.