CVE-2020-21583

Exp

An issue was discovered in hwclock.13-v2.27 allows attackers to gain escalated privlidges or execute arbitrary commands via the path parameter when setting the date.

Published: 2023-08-22 Last update: 2024-12-20 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-21583 is rated Exploit Available (56.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.52%). 2 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2020-21583

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2020-21583

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.03% 0.52% +0.49%
2 2025-11-21 0.21% 0.03% -0.17%
3 2025-11-18 — 0.21% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-21583

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.8 5.9 [email protected]

Weakness enumeration for CVE-2020-21583

OS Trackers for CVE-2020-21583

vendor priority summary link
debian not yet assigned CVE-2020-21583 not yet assigned priority: Debian including 1 source packages (util-linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-21583
redhat medium — https://access.redhat.com/security/cve/CVE-2020-21583
suse high CVE-2020-21583 severity important: SUSE including 18 source package names (libblkid-devel, libblkid-devel-static, …), 451 product×package rows across 40 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 7, … (40 product lines)): Known Not Affected 451. https://www.suse.com/security/cve/CVE-2020-21583/
ubuntu low CVE-2020-21583 low priority: Ubuntu including 1 source packages (util-linux), 12 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 10, needed 1, released 1. https://ubuntu.com/security/CVE-2020-21583

Affected software / configurations for CVE-2020-21583

Vendor Product Version Raw CPE
kernel util-linux < 2.27 cpe:2.3:a:kernel:util-linux:*:*:*:*:*:*:*:*

References for CVE-2020-21583

cvelogic Threat Intelligence