Security Resilience

CVE-2023-32221

Easeus Todo Backup 20220111.390

Published
12 June 2023
Modified
04 January 2025
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0016 5th percentile
Risk Priority 59 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-32221 is a high-severity Incorrect Default Permissions (CWE-276) vulnerability in Easeus Todo Backup. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Private Keys (T1552.004); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

EaseUS Todo Backup version 20220111.390 - An omission during installation may allow a local attacker to perform privilege escalation.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1552.004 Private Keys Credential Access
Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials.
T1574.005 Executable Installer File Permissions Weakness Stealth
Adversaries may execute their own malicious payloads by hijacking the binaries used by an installer.
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
T1574.010 Services File Permissions Weakness Stealth
Adversaries may execute their own malicious payloads by hijacking the binaries used by services.
T1574.011 Services Registry Permissions Weakness Stealth
Adversaries may execute their own malicious payloads by hijacking the Registry entries used by services.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-27462Shared CWE-276
CVE-2026-57924Shared CWE-276
CVE-2025-3617Shared CWE-276
CVE-2026-16247Shared CWE-276
CVE-2023-42133Shared CWE-276
CVE-2025-30465Shared CWE-276
CVE-2023-38370Shared CWE-276
CVE-2023-38294Shared CWE-276
CVE-2025-53813Shared CWE-276
CVE-2024-27149Shared CWE-276

Affected Assets

easeus
todo backup
20220111.390

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 7 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Likely Mitigating Controls

Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-276

Access control policy can specify and enforce secure default permissions for resources.

addresses: CWE-276

Guides setting of default permissions to the minimum required level.

addresses: CWE-276

Establishes requirements for appropriate default permissions on system resources as part of configuration management.

addresses: CWE-276

Baseline establishment and updates on install/upgrade ensure correct default permissions rather than insecure ones.

addresses: CWE-276

Requiring the most restrictive settings instead of defaults prevents incorrect default permissions on resources.

addresses: CWE-276

Requires documented processes that include setting and maintaining correct default permissions for configuration items.

addresses: CWE-276

Requires addressing secure default permissions in physical and environmental protection controls.

addresses: CWE-276

Tailoring explicitly overrides or scopes default permission assignments in the baseline to match the system's actual risk and operational needs.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-01 full match
blocks

Hardened baselines and configuration management explicitly require correct default file permissions.

PR.AA-05 mostly match
blocks

Defining and enforcing least-privilege access permissions directly prevents overly permissive defaults at install time.

ID.AM-08 partial match
blocks

Lifecycle management can encompass permission settings, yet the control is too broad to specifically mitigate incorrect defaults.

PR.PS-06 partial match
blocks

Secure SDLC practices include establishing secure defaults, but address only the development-phase portion of the weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

A.8.29's combined programme (code review, static analysis, vulnerability scanning, penetration testing) reaches CWE-276 from both SOURCE (installer scripts setting chmod/icacls are visible in code) and RUNTIME (pen tests and config scans routinely flag world-writable files); the remainder is bounded and nameable — binary-only third-party installers where source reach does not apply, and permission issues inherited from external configuration rather than the installer itself.

removes

A.8.3 mandates access restriction including read/write/execute permissions per identity (guidance items b–d), so applying it to a system whose files were installed world-writable requires tightening those permissions, which removes the weakness as it exists in the operational system; the remainder is the product's installation process itself, which A.8.3 does not govern and which can re-introduce the flaw on reinstall or upgrade.

blocks

Standard templates that restrict access to utility programs and host parameter settings prevent the assignment of overly permissive default permissions on critical resources.

prevents

A.5.37 mandates documented operating procedures that explicitly include 'secure installation and configuration of systems,' so a well-implemented procedure specifying correct file permissions during installation prevents many instances of CWE-276; however, the procedures are fallible human practice, and many observed instances arise from vendor installer defaults the organization's procedure does not reach, leaving a nameable remainder — the same practice-not-mechanism boundary that graded A.8.28 partial.

prevents

Training installers and developers on secure default permissions reduces instances where world-writable or otherwise incorrect permissions are set during installation, but the practice is fallible and the strongest control for this weakness is configuration management establishing secure installation baselines; training reaches a minority of instances.

prevents

A.8.30 carries its effect through the contractual requirements for secure design, coding and testing practices (referencing 8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-276 is such an ordinary weakness, and the clause reaches it at the same `partial` rung the owner set for A.8.30 -> CWE-134, with the same ceiling and the same fallible-practice remainder.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.

Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.

Windows Server 2016 (2 rules)
  • V-224833 Permissions for program file directories must conform to minimum requirements. blocks CWE-276
  • V-224834 Permissions for the Windows installation directory must conform to minimum requirements. blocks CWE-276
Windows Server 2019 (2 rules)
  • V-205735 Windows Server 2019 permissions for program file directories must conform to minimum requirements. blocks CWE-276
  • V-205736 Windows Server 2019 permissions for the Windows installation directory must conform to minimum requirements. blocks CWE-276

References