CVE-2022-38130
SQLi in Keysight Sensor Management Server 2.4.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
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 1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
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.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-40732
Vulnerability Data
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
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation of the file-path parameter to reject UNC paths before smsRestoreDatabaseZip accepts untrusted input.
Enforces authorization checks on the restore-database method so unauthenticated remote callers cannot invoke it.
Limits privileges of the ResourceManager process so that even a supplied UNC path cannot read or restore arbitrary remote archives.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.
Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
The same secure-coding and static-analysis activities surface missing neutralization of SQL metacharacters before the system is accepted.
Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.
Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.
Secure-coding rules and security testing phases mandate the use of parameterized queries or equivalent escaping, preventing the construction of dynamic SQL statements from untrusted input.
Language-specific secure coding rules, peer review and SAST together prevent the construction of SQL statements from untrusted data without proper parameterization or escaping.