CVE-2019-9867
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 · uneditedAn issue was discovered in the Web Console in Veritas NetBackup Appliance through 3.1.2. The proxy server password is displayed to an administrator.
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 confidenceThe Web Console in Veritas NetBackup Appliance through version 3.1.2 exposes the proxy server password in plaintext to authenticated administrators viewing certain interface pages, allowing unauthorized credential access.
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<= 3.1.2CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine NetBackup Appliance versionAccess the appliance management console or web UI and navigate to the About/Version information section. Alternatively, run the command 'nbac --version' or check the appliance support bundle for version details.Affected if The installed version is 3.1.2 or any earlier version.
-
Verify Web Console is accessibleLog into the NetBackup Appliance Web Console as an administrator and navigate through the interface pages, particularly settings related to network or proxy configuration.Affected if The Web Console is accessible and displays configuration pages to authenticated administrators.
-
Confirm proxy server is configuredCheck the Web Console for proxy server settings. Look in Network Settings, Advanced Settings, or similar configuration areas where proxy authentication credentials may be stored.Affected if A proxy server is configured with authentication credentials stored in the appliance.
-
Inspect for plaintext password exposureWhile logged in as an administrator, view the proxy server configuration pages in the Web Console. Examine the HTML source of these pages if possible to see if password fields contain plaintext values rather than masked characters.Affected if The proxy server password is displayed in plaintext rather than being masked or hidden in the interface.
A user is affected if they run NetBackup Appliance version 3.1.2 or earlier, have the Web Console enabled, and have a proxy server configured with credentials that are visible in plaintext in the interface.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable or mask the proxy server password display in the Web Console UI and ensure sensitive credentials are never transmitted to client-side interfaces.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9867 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-9867 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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