GHSA-77g3-3j5w-64w4
Vulnerability from github
Published
2021-04-07 20:36
Modified
2024-09-06 20:16
Severity ?
5.5 (Medium) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
6.8 (Medium) - CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
6.8 (Medium) - CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Summary
Exposure of Resource to Wrong Sphere and Insecure Temporary File in Ansible
Details
A flaw was found in Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when using modules which decrypts vault files such as assemble, script, unarchive, win_copy, aws_s3 or copy modules. The temporary directory is created in /tmp leaves the s ts unencrypted. On Operating Systems which /tmp is not a tmpfs but part of the root partition, the directory is only cleared on boot and the decryp emains when the host is switched off. The system will be vulnerable when the system is not running. So decrypted data must be cleared as soon as possible and the data which normally is encrypted ble.
{ "affected": [ { "package": { "ecosystem": "PyPI", "name": "ansible" }, "ranges": [ { "events": [ { "introduced": "2.7.0a1" }, { "fixed": "2.7.17" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "PyPI", "name": "ansible" }, "ranges": [ { "events": [ { "introduced": "2.8.0a1" }, { "fixed": "2.8.11" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "PyPI", "name": "ansible" }, "ranges": [ { "events": [ { "introduced": "2.9.0a1" }, { "fixed": "2.9.7" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2020-10685" ], "database_specific": { "cwe_ids": [ "CWE-377", "CWE-459", "CWE-668" ], "github_reviewed": true, "github_reviewed_at": "2021-04-05T14:11:30Z", "nvd_published_at": "2020-05-11T14:15:00Z", "severity": "MODERATE" }, "details": "A flaw was found in Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when using modules which decrypts vault files such as assemble, script, unarchive, win_copy, aws_s3 or copy modules. The temporary directory is created in /tmp leaves the s ts unencrypted. On Operating Systems which /tmp is not a tmpfs but part of the root partition, the directory is only cleared on boot and the decryp emains when the host is switched off. The system will be vulnerable when the system is not running. So decrypted data must be cleared as soon as possible and the data which normally is encrypted ble.", "id": "GHSA-77g3-3j5w-64w4", "modified": "2024-09-06T20:16:43Z", "published": "2021-04-07T20:36:46Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2020-10685" }, { "type": "WEB", "url": "https://github.com/ansible/ansible/pull/68433" }, { "type": "WEB", "url": "https://github.com/ansible/ansible/commit/4e1fe80e681fa466626e9dea53efe6b0253ea1b2" }, { "type": "WEB", "url": "https://github.com/ansible/ansible/commit/51d2514753544a9d58cd7524e27e696b2c944fb5" }, { "type": "WEB", "url": "https://github.com/ansible/ansible/commit/e1273b6faf036ed84e4f4edee85b888a4e256aee" }, { "type": "WEB", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10685" }, { "type": "ADVISORY", "url": "https://github.com/advisories/GHSA-77g3-3j5w-64w4" }, { "type": "PACKAGE", "url": "https://github.com/ansible/ansible" }, { "type": "WEB", "url": "https://github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-1.yaml" }, { "type": "WEB", "url": "https://security.gentoo.org/glsa/202006-11" }, { "type": "WEB", "url": "https://www.debian.org/security/2021/dsa-4950" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" }, { "score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N", "type": "CVSS_V4" } ], "summary": "Exposure of Resource to Wrong Sphere and Insecure Temporary File in Ansible" }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.