CVE-2020-1740: Infoleak

Published Feb 12, 2020
·
Updated

A flaw was found in Ansible Engine when using Ansible Vault for editing encrypted files. When a user executes "ansible-vault edit", another user on the same computer can read the old and new secret, as it is created in a temporary file with mkstemp and the returned file descriptor is closed and the method writedata is called to write the existing secret in the file. This method will delete the file before recreating it insecurely.

Other sources

When a user executes "ansible-vault edit", another user on the same computer can read the old and new secret, as it is created a temporary file with mkstemp and the returned file descriptor is closed and the method writedata is called to write the existing secret in the file. This method will delete the file before recreate it insecurely.

Red Hat

Affected Software

26 affected componentsFixes available
redhat/ansible<0:2.7.17-1.el7ae
0:2.7.17-1.el7ae
redhat/ansible<0:2.8.11-1.el7ae
0:2.8.11-1.el7ae
redhat/ansible<0:2.8.11-1.el8ae
0:2.8.11-1.el8ae
redhat/ansible<0:2.9.7-1.el7ae
0:2.9.7-1.el7ae
redhat/ansible<0:2.9.7-1.el8ae
0:2.9.7-1.el8ae
debian/ansible
2.7.7+dfsg-1+deb10u12.7.7+dfsg-1+deb10u22.10.7+merged+base+2.10.8+dfsg-17.3.0+dfsg-17.7.0+dfsg-3
redhat/ansible-engine<2.7.17
2.7.17
redhat/ansible-engine<2.8.11
2.8.11
redhat/ansible-engine<2.9.7
2.9.7
pip/ansible>=2.9.0a1<2.9.7
2.9.7
pip/ansible>=2.8.0a1<2.8.11
2.8.11
pip/ansible<2.7.17
2.7.17
redhat ansible<2.7.17
redhat ansible>=2.8.0<2.8.11
redhat ansible>=2.9.0<2.9.7
redhat Ansible Tower<=3.3.4
redhat Ansible Tower>=3.3.5<=3.4.5
redhat Ansible Tower>=3.5.0<=3.5.5
redhat Ansible Tower>=3.6.0<=3.6.3
redhat CloudForms Management Engine=5.0
redhat Openstack=13
Debian Debian Linux=8.0
Debian Debian Linux=10.0
Fedoraproject Fedora=30
Fedoraproject Fedora=31
Fedoraproject Fedora=32

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/ansible to a version that resolves this vulnerability.

    Fixed in 0:2.7.17-1.el7ae
  2. Upgrade

    Upgrade redhat/ansible to a version that resolves this vulnerability.

    Fixed in 0:2.8.11-1.el7ae
  3. Upgrade

    Upgrade redhat/ansible to a version that resolves this vulnerability.

    Fixed in 0:2.8.11-1.el8ae
  4. Upgrade

    Upgrade redhat/ansible to a version that resolves this vulnerability.

    Fixed in 0:2.9.7-1.el7ae
  5. Upgrade

    Upgrade redhat/ansible to a version that resolves this vulnerability.

    Fixed in 0:2.9.7-1.el8ae
  6. Upgrade

    Upgrade debian/ansible to a version that resolves this vulnerability.

    Fixed in 2.7.7+dfsg-1+deb10u1Fixed in 2.7.7+dfsg-1+deb10u2Fixed in 2.10.7+merged+base+2.10.8+dfsg-1Fixed in 7.3.0+dfsg-1Fixed in 7.7.0+dfsg-3
  7. Upgrade

    Upgrade redhat/ansible-engine to a version that resolves this vulnerability.

    Fixed in 2.7.17
  8. Upgrade

    Upgrade redhat/ansible-engine to a version that resolves this vulnerability.

    Fixed in 2.8.11
  9. Upgrade

    Upgrade redhat/ansible-engine to a version that resolves this vulnerability.

    Fixed in 2.9.7
  10. Upgrade

    Upgrade pip/ansible to a version that resolves this vulnerability.

    Fixed in 2.9.7
  11. Upgrade

    Upgrade pip/ansible to a version that resolves this vulnerability.

    Fixed in 2.8.11
  12. Upgrade

    Upgrade pip/ansible to a version that resolves this vulnerability.

    Fixed in 2.7.17
  13. Configuration

    Do not use the 'edit' option of the 'ansible-vault' command line tool, since during 'ansible-vault edit' it deletes and recreates the file insecurely and other users on the same computer may read the old/new secret from the temporary file.

    ansible-vault command line tool ansible-vault edit usage = avoid

Event History

Feb 18, 2020
CVE Published
12:00 AM
Mar 16, 2020
CVE Published
via MITRE·03:07 PM
Data Sourced
via MITRE·03:07 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software
Apr 7, 2021
Advisory Published
via GitHub·09:47 PM

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2020-1740?

CVE-2020-1740 is a vulnerability found in Ansible Engine when using Ansible Vault for editing encrypted files.

2

What is the severity of CVE-2020-1740?

The severity of CVE-2020-1740 is low, with a severity value of 3.9.

3

Which software versions are affected by CVE-2020-1740?

Ansible versions 2.7.17-1.el7ae, 2.8.11-1.el7ae, 2.8.11-1.el8ae, 2.9.7-1.el7ae, and 2.9.7-1.el8ae are affected by CVE-2020-1740.

4

How can an attacker exploit CVE-2020-1740?

An attacker can exploit CVE-2020-1740 by executing "ansible-vault edit" on a system where another user can read the old and new secret.

5

Are there any references available for CVE-2020-1740?

Yes, you can find references for CVE-2020-1740 at the following links: [1] [2] [3].

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203