Skip to content
Fencer Intel
medium 6.6

CVE-2021-3701 json

ansible-runner has default temporary files written to world R/W locations

published 4y ago modified 4mo ago also GHSA-wwch-cmqr-hhrm , PYSEC-2022-43067 , EUVD-2022-0004

cvss
6.6
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits
0
none known

Summary

A flaw was found in ansible-runner where the default temporary files configuration in ansible-2.0.0 are written to world R/W locations. This flaw allows an attacker to pre-create the directory, resulting in reading private information or forcing ansible-runner to write files as the legitimate user in a place they did not expect. The highest threat from this vulnerability is to confidentiality and integrity.

Patch / fix

  • pypi ansible-runner 2.1.0
  • ansible-runner Debian 14, Debian 13, Debian 12 2.1.1-1

debian advisories DEBIAN-CVE-2021-3701

Is CVE-2021-3701 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-3701 updated cvss 6.6

ansible-runner: Artifacts are written to world rw location by default

  • Red Hat Ceph Storage 4 ansible-runner, python3-ansible-runner
    affected: no fix available “Fix deferred”
  • Red Hat CloudForms Management Engine 5 ansible-runner, python2-ansible-runner, python3-ansible-runner Red Hat Ansible Automation Platform 1.2 ansible-runner Red Hat Ansible Automation Platform 2 ansible-runner Red Hat Ansible Tower 3 ansible-runner, python2-ansible-runner, python3-ansible-runner Red Hat OpenShift Container Platform 3.11 ansible-runner Red Hat OpenShift Container Platform 4 ansible-runner, python2-ansible-runner, python3-ansible-runner
    +4 more products
    Red Hat OpenStack Platform 13 (Queens) python2-ansible-runner Red Hat OpenStack Platform 16 (Train) python-ansible-runner, python3-ansible-runner Red Hat Satellite 6 ansible-runner, python2-ansible-runner Red Hat Virtualization 4 ansible-runner, python3-ansible-runner, python38-ansible-runner
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 6.6 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
GitHub 3.1 6.6 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
OSV 3.1 6.6 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
pypi ansible-runner
>=2.0.0, <2.1.0
2.1.0

Affected products

  • n/a ansible-runner

Classification

Weakness
  • CWE-276 Incorrect Default Permissions

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.