CVE-2020-25860
Vulnerability Scoring
Attack Complexity Details
- Attack Complexity: HIGH IMPACT
- Attack Vector: NETWORK
- Privileges Required: HIGH IMPACT
- Scope: UNCHANGED
- User Interaction: NONE
CIA Impact Definition
- Confidentiality: HIGH IMPACT
- Integrity: HIGH IMPACT
- Availability: HIGH IMPACT
CVE-2020-25860 Vulnerability Summary
The install.c module in the Pengutronix RAUC update client prior to version 1.5 has a Time-of-Check Time-of-Use vulnerability, where signature verification on an update file takes place before the file is reopened for installation. An attacker who can modify the update file just before it is reopened can install arbitrary code on the device.
Access Complexity Graph for CVE-2020-25860
Impact Analysis for CVE-2020-25860
CVE-2020-25860: Detailed Information and External References
EPSS
0.00224
EPSS %
0.60776
References
0.00224
- https://github.com/rauc/rauc/security/advisories/GHSA-cgf3-h62j-w9vv
- https://www.vdoo.com/blog/cve-2020-25860-significant-vulnerability-discovered-rauc-embedded-firmware-update-framework
CWE
CWE-367
CAPEC
0.00224
- Leveraging Race Conditions via Symbolic Links: This attack leverages the use of symbolic links (Symlinks) in order to write to sensitive files. An attacker can create a Symlink link to a target file not otherwise accessible to them. When the privileged program tries to create a temporary file with the same name as the Symlink link, it will actually write to the target file pointed to by the attackers' Symlink link. If the attacker can insert malicious content in the temporary file they will be writing to the sensitive file by using the Symlink. The race occurs because the system checks if the temporary file exists, then creates the file. The attacker would typically create the Symlink during the interval between the check and the creation of the temporary file.
- Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions: This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.
Vulnerable Configurations
-
cpe:2.3:a:pengutronix:rauc:0.1:*:*:*:*:*:*:*
cpe:2.3:a:pengutronix:rauc:0.1:*:*:*:*:*:*:*
-
cpe:2.3:a:pengutronix:rauc:0.1.1:*:*:*:*:*:*:*
cpe:2.3:a:pengutronix:rauc:0.1.1:*:*:*:*:*:*:*
-
cpe:2.3:a:pengutronix:rauc:0.2:*:*:*:*:*:*:*
cpe:2.3:a:pengutronix:rauc:0.2:*:*:*:*:*:*:*
-
cpe:2.3:a:pengutronix:rauc:0.3:*:*:*:*:*:*:*
cpe:2.3:a:pengutronix:rauc:0.3:*:*:*:*:*:*:*
-
cpe:2.3:a:pengutronix:rauc:0.4:*:*:*:*:*:*:*
cpe:2.3:a:pengutronix:rauc:0.4:*:*:*:*:*:*:*
-
cpe:2.3:a:pengutronix:rauc:1.0:-:*:*:*:*:*:*
cpe:2.3:a:pengutronix:rauc:1.0:-:*:*:*:*:*:*
-
cpe:2.3:a:pengutronix:rauc:1.0:rc1:*:*:*:*:*:*
cpe:2.3:a:pengutronix:rauc:1.0:rc1:*:*:*:*:*:*
-
cpe:2.3:a:pengutronix:rauc:1.1:*:*:*:*:*:*:*
cpe:2.3:a:pengutronix:rauc:1.1:*:*:*:*:*:*:*
-
cpe:2.3:a:pengutronix:rauc:1.2:*:*:*:*:*:*:*
cpe:2.3:a:pengutronix:rauc:1.2:*:*:*:*:*:*:*
-
cpe:2.3:a:pengutronix:rauc:1.3:*:*:*:*:*:*:*
cpe:2.3:a:pengutronix:rauc:1.3:*:*:*:*:*:*:*
-
cpe:2.3:a:pengutronix:rauc:1.4:*:*:*:*:*:*:*
cpe:2.3:a:pengutronix:rauc:1.4:*:*:*:*:*:*:*
CVSS3 Source
nvd@nist.gov
CVSS3 Type
Primary
CVSS3 Vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
Protect Your Infrastructure: 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.