CVE-2022-38130
Published: 10 August 2022
Summary
CVE-2022-38130 is a critical-severity SQL Injection (CWE-89) vulnerability in Keysight Sensor Management Server. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 0.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2022-38130 affects the smsRestoreDatabaseZip method in the com.keysight.tentacle.config.ResourceManager class used by Keysight SMS for restoring its embedded HSQLDB database. The method accepts a single file-path parameter and performs no validation against UNC paths, enabling an attacker to supply a remote ZIP archive as the restoration source. The issue is tracked under CWE-89 and carries a CVSS 3.1 base score of 9.8.
An unauthenticated remote attacker can invoke the method over the network with a UNC path such as \\attacker-host\sms\malicious.zip. Because the supplied archive becomes the new database contents, the attacker gains full control over the data that SMS subsequently loads and queries, resulting in high-impact confidentiality, integrity, and availability consequences.
The referenced Tenable advisory TRA-2022-28 provides the technical analysis of the flaw but does not detail vendor patches or configuration work-arounds within the supplied information.
EPSS scores have remained elevated, with a current value of 0.7841 and a recorded peak of 0.7944.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-40732
Vulnerability details
The com.keysight.tentacle.config.ResourceManager.smsRestoreDatabaseZip() method is used to restore the HSQLDB database used in SMS. It takes the path of the zipped database file as the single parameter. An unauthenticated, remote attacker can specify an UNC path for the database file (i.e.,…
more
\\<attacker-host>\sms\<attacker-db.zip>), effectively controlling the content of the database to be restored.
- 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.