CVE-2022-38130
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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., \\<attacker-host>\sms\<attacker-db.zip>), effectively controlling the content of the database to be restored.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe smsRestoreDatabaseZip() method in Keysight Tentacle accepts a file path parameter without authentication, allowing unauthenticated remote attackers to supply a UNC path (\\attacker-host\path\file.zip) to a malicious database ZIP file. The application will restore the attacker-controlled database, potentially enabling code execution or data manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Keysight Sensor Management Server versionLocate the installation directory for Keysight Tentacle/Sensor Management Server and check the version information in the application metadata, typically found in version.ini, about dialog, or installer logsAffected if The installed version is exactly 2.4.0
-
Determine if the smsRestoreDatabaseZip method is exposedInspect the application's API endpoints, web service definitions, or RPC interfaces to identify if the smsRestoreDatabaseZip() method is publicly accessible without authenticationAffected if The restore database function is accessible without requiring valid credentials
-
Review application logs for restore operationsExamine Keysight Tentacle application logs, typically stored in the logs directory, for entries containing 'smsRestoreDatabaseZip' or 'database restore' actionsAffected if Log entries show database restore operations from unexpected or external UNC paths (\\) that you do not recognize
-
Check for external network connections to suspicious UNC pathsReview network connection logs or use netstat/endpoint detection tools to identify any SMB connections from the Keysight server to external IP addresses, particularly to paths containing '\\' notationAffected if The server has established outbound SMB connections to unknown external hosts
-
Inspect for recent unexpected database file modificationsCheck the database storage location for Keysight Tentacle for ZIP files or database backups that were created or modified at unusual times or by unexpected processesAffected if New or modified database ZIP files exist that were not initiated by legitimate administrators
You are affected if Keysight Sensor Management Server version 2.4.0 is running AND the smsRestoreDatabaseZip functionality is exposed without authentication, particularly if logs or network logs show restore operations from external UNC paths.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRequire authentication for database restore operations and implement strict input validation to prevent UNC path or arbitrary file path usage. Consider network segmentation to limit exposure of this functionality.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-38130 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data