dbcve.org
Autopass License ServerApplication · Hpe

CVE-2025-37105

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-16
Fix available
A fix is available. Upgrade to 9.18 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An hsqldb-related remote code execution vulnerability exists in HPE AutoPass License Server (APLS) prior to 9.18.

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 · moderate confidence

A remote code execution vulnerability in HPE AutoPass License Server stems from insecure handling within the embedded hsqldb database component. This critical flaw allows unauthenticated remote attackers to execute arbitrary code on affected systems by leveraging the database's ability to execute system commands or through unsafe deserialization. The vulnerability affects versions prior to 9.18 and carries a CVSS 9.8 due to its network-exploitable nature and complete system compromise potential.

MitigationUpgrade HPE AutoPass License Server to version 9.18 or later to address the vulnerability. If immediate patching is not feasible, restrict network access to the APLS service and implement network segmentation to limit exposure.

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
Autopass License ServerApplication
Affected:< 9.18

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if HPE AutoPass License Server is installed
    Locate the APLS installation directory, typically found under /opt/ or C:\Program Files\ on Linux/Windows systems. Look for the AutoPass folder or license server binaries.
    Affected if The software is not present on the system, the user is not affected.
  2. Determine the installed version of APLS
    Check for a version file or banner within the installation directory, or run the application with a version flag if available. Common locations include a version.txt file or the application executable properties.
    Affected if The installed version is any version prior to 9.18, the user is affected.
  3. Verify the hsqldb component is present and accessible
    Inspect the APLS installation for the embedded hsqldb database files (typically .script, .data, or .properties files with hsqldb naming). Check if the database is configured to accept network connections.
    Affected if hsqldb is present and configured with network accessibility, the user is affected.
  4. Check network exposure of the APLS service
    Identify the listening port for the license server (default often 5814 or similar) and determine if the service is exposed to untrusted networks using netstat, ss, or port scanning tools.
    Affected if The APLS service is reachable from untrusted networks without proper access controls, the user is affected.

The environment is affected if HPE AutoPass License Server is installed with a version lower than 9.18 and the hsqldb-based service is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 9.18 or later
Fixed in 9.18
Interim mitigation

Upgrade HPE AutoPass License Server to version 9.18 or later to address the vulnerability. If immediate patching is not feasible, restrict network access to the APLS service and implement network segmentation to limit exposure.

Recommended fix High confidence

HPE AutoPass License Server 9.18

  1. 1. Obtain HPE AutoPass License Server version 9.18 from the official HPE support portal at support.hpe.com
  2. 2. Review the upgrade documentation provided with version 9.18
  3. 3. Perform a backup of the current APLS installation and configuration
  4. 4. Stop the HPE AutoPass License Server service
  5. 5. Install version 9.18 following the documented upgrade procedure
  6. 6. Verify the installation and ensure the service starts successfully
  7. 7. Confirm the hsqldb-related vulnerability is remediated by verifying the version and functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Autopass License Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-37105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-37105 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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