Bluedata EpicApplication · Hp

CVE-2020-7196

MEDIUM · 6.5 CVSS v3.1 Published 2020-10-26
Fix available
A fix is available. Upgrade to after 4.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
The HPE BlueData EPIC Software Platform version 4.0 and HPE Ezmeral Container Platform 5.0 use an insecure method of handling sensitive Kerberos passwords that is susceptible to unauthorized interception and/or retrieval. Specifically, they display the kdc_admin_password in the source file of the url "/bdswebui/assignusers/".

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 confidence

The HPE BlueData EPIC Software Platform 4.0 and HPE Ezmeral Container Platform 5.0 contain a sensitive information disclosure vulnerability where the Kerberos administrator password (kdc_admin_password) is exposed in the client-side source code of the '/bdswebui/assignusers/' web UI endpoint. This allows an attacker with network access to retrieve the plaintext Kerberos admin credentials from the browser or intercepted HTTP responses.

MitigationImmediately rotate the exposed kdc_admin_password and any related Kerberos credentials. Remove the credential from being transmitted to the frontend by refactoring server-side code to not expose sensitive Kerberos configuration values to the web UI. Apply any HPE-supplied patches for these products.

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
Bluedata EpicApplication
Affected:<= 4.0
Ezmeral Container PlatformApplication
Affected:= 5.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 installed product and version
    Access the web UI or check system documentation to confirm whether HPE BlueData EPIC Software Platform or HPE Ezmeral Container Platform is deployed, and note the exact version number
    Affected if The product is HPE BlueData EPIC version 4.0 or lower, or HPE Ezmeral Container Platform version 5.0
  2. Confirm web UI accessibility
    Attempt to access the /bdswebui/assignusers/ endpoint via browser or HTTP tool (such as curl) on the system where the product is running
    Affected if The endpoint returns an HTTP 200 response and is accessible over the network
  3. Inspect HTTP response for exposed credentials
    Use browser developer tools (Network tab) or an HTTP interception tool to capture the full response from /bdswebui/assignusers/ and search within the response body for the string 'kdc_admin_password'
    Affected if The response contains 'kdc_admin_password' with a plaintext value (visible as a string literal in the client-side source code)
  4. Verify credential exposure in source
    View the page source or response body directly and search for any Kerberos-related configuration values being transmitted to the client-side
    Affected if Sensitive Kerberos configuration values, particularly the administrator password, appear in plaintext within the returned HTML or JavaScript

A user is affected if they are running the specified product versions and the /bdswebui/assignusers/ endpoint returns the kdc_admin_password in plaintext within the HTTP response body.

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
Upgrade available Upgrade to a release after 4.0
Interim mitigation

Immediately rotate the exposed kdc_admin_password and any related Kerberos credentials. Remove the credential from being transmitted to the frontend by refactoring server-side code to not expose sensitive Kerberos configuration values to the web UI. Apply any HPE-supplied patches for these products.

Fix this in Bluedata Epic Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7196 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-7196 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