CVE-2024-25830
Published: 29 February 2024
Summary
CVE-2024-25830 is a critical-severity Path Traversal (CWE-22) vulnerability in F-Logic Datacube3 Firmware. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 2.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
F-logic DataCube3 version 1.0 is affected by an incorrect access control vulnerability caused by improper directory access restrictions. The flaw is tracked as CVE-2024-25830 with associated CWEs CWE-22 and CWE-284, and carries a CVSS 3.1 base score of 9.8 reflecting network-accessible impact to confidentiality, integrity, and availability without any required authentication or user interaction.
An unauthenticated remote attacker can exploit the issue by supplying a URI that directly references the path of the configuration file. Successful exploitation grants the attacker the ability to retrieve the root and administrative account passwords stored within that file.
The EPSS score for this CVE is currently 0.3912 with an identical peak value, indicating moderate exploitation probability but no material upward trajectory after disclosure. Details of the flaw were published in a technical report hosted at neroteam.com.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-23137
Vulnerability details
F-logic DataCube3 v1.0 is vulnerable to Incorrect Access Control due to an improper directory access restriction. An unauthenticated, remote attacker can exploit this, by sending a URI that contains the path of the configuration file. A successful exploit could allow…
more
the attacker to extract the root and admin password.
- 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.
The access control policy and procedures directly mandate and enforce proper access control mechanisms across the organization.
Device lock enforces restricted access until re-authentication, directly reducing unauthorized use of active sessions.
Supervision and review of access control activities directly detects and remediates improper access configurations or usages.
Explicitly identifying and documenting actions permitted without identification or authentication enforces proper access control boundaries by defining justified exceptions.
By automatically labeling outputs with security attributes, the control supports attribute-based enforcement and reduces exploitability of improper access control weaknesses.
Associating and retaining security attributes with data directly supports enforcement of access control decisions across storage, processing, and transmission.
Requiring prior authorization for each remote access type prevents improper access control over remote connections.
Requiring authorization of wireless access before allowing connections enforces proper access control for this access method.