CVE-2020-10744 Vulnerability Analysis & Exploit Details

CVE-2020-10744
Vulnerability Scoring

5.0

/10

Medium Risk

The vulnerability CVE-2020-10744 could compromise system integrity but typically requires user interaction to be exploited.

Attack Complexity Details

Attack Complexity: High
Exploits require significant effort and special conditions.
Attack Vector: Local
Vulnerability requires local system access.
Privileges Required: Low
Some privileges are necessary to exploit the vulnerability.
Scope: Changed
Successful exploitation can impact components beyond the vulnerable component.
User Interaction: Required
User interaction is necessary for successful exploitation.

CVE-2020-10744 Details

Status: Modified

Last updated: 🕒 07 Nov 2023, 03:14 UTC
Originally published on: 🕑 15 May 2020, 14:15 UTC

Time between publication and last update: 1270 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L

CVE-2020-10744 Vulnerability Summary

CVE-2020-10744: An incomplete fix was found for the fix of the flaw CVE-2020-1733 ansible: insecure temporary directory when running become_user from become directive. The provided fix is insufficient to prevent the race condition on systems using ACLs and FUSE filesystems. Ansible Engine 2.7.18, 2.8.12, and 2.9.9 as well as previous versions are affected and Ansible Tower 3.4.5, 3.5.6 and 3.6.4 as well as previous versions are affected.

Assessing the Risk of CVE-2020-10744

Access Complexity Graph

The exploitability of CVE-2020-10744 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2020-10744

This vulnerability, CVE-2020-10744, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2020-10744, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2020-10744, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

Confidentiality: Low
CVE-2020-10744 could lead to minor leaks of non-critical information without major privacy breaches.
Integrity: Low
Exploiting CVE-2020-10744 may cause minor changes to data without severely impacting its accuracy.
Availability: Low
CVE-2020-10744 may slightly degrade system performance without fully affecting service availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.044% (probability of exploit)

EPSS Percentile: 15.45% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 84.55% of others.

CVE-2020-10744 References

External References

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10744

CWE Common Weakness Enumeration

CWE-377

CAPEC Common Attack Pattern Enumeration and Classification

Explore for Predictable Temporary File Names CAPEC-149 An attacker explores a target to identify the names and locations of predictable temporary files for the purpose of launching further attacks against the target. This involves analyzing naming conventions and storage locations of the temporary files created by a target application. If an attacker can predict the names of temporary files they can use this information to mount other attacks, such as information gathering and symlink attacks.
Screen Temporary Files for Sensitive Information CAPEC-155 An adversary exploits the temporary, insecure storage of information by monitoring the content of files used to store temp data during an application's routine execution flow. Many applications use temporary files to accelerate processing or to provide records of state across multiple executions of the application. Sometimes, however, these temporary files may end up storing sensitive information. By screening an application's temporary files, an adversary might be able to discover such sensitive information. For example, web browsers often cache content to accelerate subsequent lookups. If the content contains sensitive information then the adversary could recover this from the web cache.

Vulnerable Configurations

cpe:2.3:a:redhat:ansible:2.7.0:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.0:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.0:rc1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.0:rc1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.0:rc2:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.0:rc2:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.0:rc3:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.0:rc3:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.0:rc4:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.0:rc4:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.0:beta1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.0:beta1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.0:alpha1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.0:alpha1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.1:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.1:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.2:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.2:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.3:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.3:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.4:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.4:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.5:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.5:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.6:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.6:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.7:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.7:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.8:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.8:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.9:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.9:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.10:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.10:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.11:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.11:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.12:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.12:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.13:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.13:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.14:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.14:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.15:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.15:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.16:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.16:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.17:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.17:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.18:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.7.18:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.0:-:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.0:-:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.0:a1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.0:a1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.0:b2:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.0:b2:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.0:rc1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.0:rc1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.0:rc2:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.0:rc2:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.0:rc3:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.0:rc3:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.1:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.1:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.2:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.2:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.3:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.3:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.4:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.4:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.5:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.5:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.6:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.6:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.7:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.7:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.8:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.8:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.9:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.9:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.12:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.8.12:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:-:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:-:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:b1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:b1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:rc1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:rc1:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:rc2:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:rc2:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:rc3:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:rc3:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:rc4:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:rc4:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:rc5:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.0:rc5:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.1:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.1:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.2:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.2:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.3:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.3:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.4:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.4:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.5:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.5:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.6:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.6:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.9:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible:2.9.9:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.4.0:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.4.0:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.4.1:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.4.1:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.4.2:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.4.2:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.4.3:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.4.3:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.4.4:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.4.4:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.4.5:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.4.5:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.0:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.0:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.1:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.1:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.2:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.2:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.3:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.3:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.4:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.4:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.5:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.5:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.6:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.5.6:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.6.0:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.6.0:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.6.1:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.6.1:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.6.2:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.6.2:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.6.3:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.6.3:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.6.4:*:*:*:*:*:*:*
cpe:2.3:a:redhat:ansible_tower:3.6.4:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2020-10744: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

CVE-2025-3801 – A vulnerability was found in songquanpeng one-api up to 0.6.10. It has been classified as problematic. This affects an unknown part of the componen...
CVE-2025-3800 – A vulnerability has been found in WCMS 11 and classified as critical. Affected by this vulnerability is an unknown functionality of the file app/co...
CVE-2025-3799 – A vulnerability, which was classified as critical, was found in WCMS 11. Affected is an unknown function of the file app/controllers/AnonymousContr...
CVE-2025-3798 – A vulnerability, which was classified as critical, has been found in WCMS 11. This issue affects the function sub of the file app/admin/AdvadminCon...
CVE-2025-3661 – The SB Chart block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘className’ parameter in all versions up to, and inclu...