dbcve.org
Nonstop Safeguard H SeriesApplication · Hp

CVE-2018-7119

HIGH · 7.0 CVSS v3.0 Published 2019-05-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/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 Local Disclosure of Sensitive Information vulnerability was identified in HPE NonStop Safeguard earlier than version SPR T9750L01^AIC or T9750H05^AIH, and later versions when the PASSWORD-PROMPT configuration attribute is not set to BLIND; all versions on H-series. STDSEC-STANDARD SECURITY PROD All prior versions before T6533L01^ADU or T6533H05^ADW, and later versions when the PASSWORD-PROMPT configuration attribute is not set to BLIND and all versions on H-series . Note that some commands in NonStop Safeguard and NonStop Standard Security software require username and password to be passed as command line parameters, which may lead to a local disclosure of the credentials.

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

HPE NonStop Safeguard and NonStop Standard Security allow usernames and passwords to be passed as command-line parameters when the PASSWORD-PROMPT configuration attribute is not set to BLIND. This enables local users to discover credentials through process inspection, command history, or other local observation methods, resulting in sensitive information disclosure.

MitigationSet the PASSWORD-PROMPT configuration attribute to BLIND to prevent credential exposure via command-line parameters, and upgrade to version SPR T9750L01^AIC or later (NonStop Safeguard) or T6533L01^ADU or later (NonStop Standard Security).

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
Nonstop Safeguard H SeriesApplication
Affected:all versions
Nonstop Safeguard J SeriesApplication
Affected:< t9750h05\^aih
Nonstop Safeguard L SeriesApplication
Affected:< t9750l01\^aic
Nonstop Standard Security H SeriesApplication
Affected:all versions
Nonstop Standard Security J SeriesApplication
Affected:<= t6533h05\^adw
Nonstop Standard Security L SeriesApplication
Affected:< t6533l01\^adu

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

CVSS:3.0/AV:L/AC:H/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. Identify the installed NonStop product and version
    Use the system's software inventory or version reporting mechanism to determine if HPE NonStop Safeguard or NonStop Standard Security is installed, and note the exact version string (for example, run the product's version command or check the installed software package)
    Affected if The product is HPE NonStop Safeguard or NonStop Standard Security with a version that falls within the affected ranges (H Series all versions, J Series < t9750h05/^aih for Safeguard or <= t6533h05/^adw for Standard Security, L Series < t9750l01/^aic for Safeguard or < t6533l01/^adu for Standard Secu
  2. Locate the PASSWORD-PROMPT configuration setting
    Access the NonStop Safeguard or Standard Security configuration file (typically found in the product's configuration directory) and search for the PASSWORD-PROMPT attribute
    Affected if The PASSWORD-PROMPT attribute is present but is NOT set to BLIND, or the PASSWORD-PROMPT attribute is absent entirely from the configuration
  3. Inspect running processes for exposed credentials
    Use system process inspection commands (such as process listing utilities available on NonStop systems) to examine running processes and their command-line arguments, looking for any processes that show username or password strings in the command line
    Affected if Any Safeguard or Standard Security processes are observed with username or password parameters visible in the command-line arguments
  4. Review command history for credential exposure
    Examine the system's command history logs or audit trails for recent commands that invoked Safeguard or Standard Security utilities with username and password arguments passed directly on the command line
    Affected if Command history shows recent use of commands with credentials passed as visible command-line arguments

A system is affected if it runs HPE NonStop Safeguard or Standard Security in an affected version range AND has PASSWORD-PROMPT configured to something other than BLIND (or not configured at all), allowing credentials to be observable in process listings or command history.

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

Set the PASSWORD-PROMPT configuration attribute to BLIND to prevent credential exposure via command-line parameters, and upgrade to version SPR T9750L01^AIC or later (NonStop Safeguard) or T6533L01^ADU or later (NonStop Standard Security).

Fix this in Nonstop Safeguard H Series Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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