dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-37112

MEDIUM · 6.0 CVSS v3.1 Published 2025-07-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
A vulnerability was discovered in the storage policy for certain sets of encryption keys in the HPE Telco Network Function Virtual Orchestrator. Successful Exploitation could lead to unauthorized parties gaining access to sensitive system information.

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

This vulnerability exists in the storage policy mechanism for certain encryption keys within HPE Telco Network Function Virtual Orchestrator. The weakness allows unauthorized parties to potentially access sensitive system information through improper key storage protection. The exact mechanism of the policy failure is not specified in available documentation.

MitigationReview and harden encryption key storage policies according to HPE guidance; ensure encryption keys are stored in secure enclaves or hardware security modules with proper access controls; rotate any potentially compromised keys.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

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 Telco Network Function Virtual Orchestrator is installed
    Locate the product installation directory or check for running processes named 'hpe-tnfo' or similar HPE NFVO components. Use 'ps aux | grep -i hpe' or check standard installation paths like /opt/hpe/nfvo or /opt/hpe/tnfo.
    Affected if The product is present on the system.
  2. Determine the installed version
    Check the product version via 'rpm -q hpe-nfvo' or 'dpkg -l hpe-nfvo', or examine version files in the installation directory such as VERSION.txt, about.properties, or a version file in /opt/hpe/nfvo/.
    Affected if The installed version matches or falls within the affected version range for this CVE.
  3. Locate encryption key storage configuration
    Search for configuration files related to key storage: look in /opt/hpe/nfvo/config/ for files named keystore.properties, encryption-config.xml, or policy-config.xml. Use 'find /opt/hpe -name *key* -o -name *policy*' to locate relevant files.
    Affected if Key storage configuration files exist and contain unencrypted or improperly protected key references.
  4. Inspect encryption key storage policy settings
    Examine the identified configuration files for the 'storage.policy', 'key.storage.mode', or 'key.encryption.method' settings. Look for values indicating keys are stored in plaintext, file-system based storage, or without hardware security module (HSM) protection.
    Affected if The policy shows keys are stored without HSM or secure enclave protection (e.g., 'software', 'file', 'none', or missing 'hsm'/'enclave' settings).
  5. Verify access controls on key storage locations
    Check file permissions on the key storage directories and files using 'ls -la' and 'getfacl'. Examine if the key files are readable by non-privileged users or if ACLs permit unauthorized access.
    Affected if Key storage files or directories have overly permissive access (world-readable, group-readable by non-admin groups, or missing restrictive ACLs).

A user is affected if HPE Telco NFVO is installed with a vulnerable version and encryption keys are stored without hardware security module or secure enclave protection, or with weak access controls on the key storage location.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and harden encryption key storage policies according to HPE guidance; ensure encryption keys are stored in secure enclaves or hardware security modules with proper access controls; rotate any potentially compromised keys.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-37112 — 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-37112 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