dbcve.org
Autopass License ServerApplication · Hpe

CVE-2024-51768

HIGH · 8.0 CVSS v3.1 Published 2025-07-14
Fix available
A fix is available. Upgrade to 9.17 or later.
See remediation →
82/100
Remediation priority · High
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.17.

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 exists in HPE AutoPass License Server stemming from the hsqldb (HyperSQL Database) component. The vulnerability allows attackers to execute arbitrary code on the affected system by exploiting the embedded database service. Versions of APLS prior to 9.17 are vulnerable.

MitigationUpgrade HPE AutoPass License Server to version 9.17 or later to address the hsqldb RCE vulnerability. As a temporary compensating control, restrict network access to the APLS management interfaces and monitor for unusual database-related activity.

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.17

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/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. Check HPE AutoPass License Server version
    Locate the APLS installation directory and check the version file or use the product's version information utility. Common locations include /opt/hp/autopass or C:\Program Files\HPE\AutoPass License Server. Look for a version.txt, about dialog, or use the APLS admin console to view version information.
    Affected if The installed version is below 9.17 (for example, 9.10, 9.15, etc.)
  2. Identify hsqldb component presence
    Examine the APLS installation directory for the hsqldb.jar file or related HyperSQL Database libraries. This is typically found in the lib or third-party subdirectory within the APLS installation path.
    Affected if The hsqldb JAR file exists in the APLS installation directory, indicating the vulnerable component is present
  3. Verify hsqldb network exposure
    Check APLS configuration files (such as server.xml, web.xml, or database connection configuration) to determine if the embedded hsqldb database is configured with network listening enabled rather than in-memory or file-based mode only.
    Affected if hsqldb is configured to accept remote connections or is exposed via a network port that could be reached by attackers
  4. Assess management interface accessibility
    Review network configuration or firewall rules to determine if the APLS management web interface (typically ports 5814, 8080, or 8443) is exposed to untrusted networks or the internet.
    Affected if The APLS management interfaces are accessible from untrusted networks without proper access controls

You are affected if HPE AutoPass License Server version is below 9.17 AND the hsqldb component is present and 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.17 or later
Fixed in 9.17
Interim mitigation

Upgrade HPE AutoPass License Server to version 9.17 or later to address the hsqldb RCE vulnerability. As a temporary compensating control, restrict network access to the APLS management interfaces and monitor for unusual database-related activity.

Recommended fix High confidence

9.17 or later

  1. Upgrade HPE AutoPass License Server to version 9.17 or later to remediate the hsqldb-related remote code execution vulnerability.
  2. After upgrading, verify that the HPE AutoPass License Server is running the updated version.
  3. Consult HPE support documentation (support.hpe.com) for specific upgrade instructions and any prerequisites.

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-2024-51768 — 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-2024-51768 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