CVE-2023-45499
Published: 27 October 2023
Summary
CVE-2023-45499 is a critical-severity Use of Hard-coded Credentials (CWE-798) vulnerability in Vinchin Vinchin Backup And Recovery. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 1.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
VinChin Backup & Recovery versions 5.0.*, 6.0.*, 6.7.*, and 7.0.* contain hardcoded credentials, tracked as CVE-2023-45499 with a CVSS 3.1 score of 9.8. The flaw is classified under CWE-798 and affects the product's authentication mechanism, allowing unauthenticated network access to sensitive functions without requiring user interaction.
An attacker with network reachability can leverage the embedded credentials to authenticate directly to the appliance. Public disclosures demonstrate that this access leads to remote code execution, including chained command injection primitives that permit full system compromise and arbitrary command execution on the backup server.
Multiple exploit artifacts and technical analyses have been published on PacketStorm, Full Disclosure, and Leakix, detailing working remote code execution chains against the affected versions. The associated EPSS score sits at 0.6949 with no material post-disclosure increase from a lower baseline. No vendor advisory or patch information appears among the referenced sources.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-49791
Vulnerability details
VinChin Backup & Recovery v5.0.*, v6.0.*, v6.7.*, and v7.0.* was discovered to contain hardcoded credentials.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
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.
Enables users to notice when hard-coded credentials have been exploited for unauthorized access.
Security training explicitly warns against hard-coded credentials, lowering their use in systems.
Policy and procedures prohibit hard-coded credentials in favor of managed authentication.
External identity providers eliminate the need for hard-coded credentials in applications.
Changing default authenticators prior to first use and protecting content prevents use of hard-coded credentials.
Central credential stores and rotation policies remove the need for hard-coded credentials in configuration files or code.
Intelligence programs surface reports of campaigns that abuse hard-coded credentials in products, prompting removal or replacement and thereby reducing successful exploitation.
Planned investment enables secure credential storage and management systems instead of hard-coded credentials.