dbcve.org
Privileged Access ManagerApplication · Broadcom

CVE-2019-7392

CRITICAL · 9.1 CVSS v3.0 Published 2019-02-26
Fix available
A fix is available. Upgrade to after 3.2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 improper authentication vulnerability in CA Privileged Access Manager 3.x Web-UI jk-manager and jk-status allows a remote attacker to gain sensitive information or alter configuration.

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

An improper authentication vulnerability in CA Privileged Access Manager 3.x Web-UI components (jk-manager and jk-status) allows remote unauthenticated attackers to bypass authentication and access sensitive information or modify system configuration.

MitigationApply available patches from CA/Broadcom for PAM 3.x and ensure jk-manager and jk-status endpoints require proper authentication or are network-segmented from untrusted networks.

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
Privileged Access ManagerApplication
Affected:>= 3.0.1, <= 3.0.3>= 3.1.1, <= 3.1.2>= 3.2.0, <= 3.2.1

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Confirm CA/Broadcom Privileged Access Manager is installed
    Check for the presence of CA Privileged Access Manager or Broadcom PAM in your environment by reviewing installed software, service listings, or consulting your asset inventory
    Affected if The software is not present in your environment, you are likely not affected by this specific CVE
  2. Identify the installed version of PAM
    Locate the installed version number of CA/Broadcom Privileged Access Manager through the product interface, command line, or configuration files, then compare it to the affected ranges: 3.0.1-3.0.3, 3.1.1-3.1.2, or 3.2.0-3.2.1
    Affected if The installed version falls within any of these ranges, your environment contains the vulnerable version
  3. Determine if jk-manager endpoint is exposed
    Attempt to access the /jk-manager Web-UI endpoint on your PAM server (typically via HTTP/HTTPS on the management port) without providing credentials
    Affected if The endpoint is accessible and returns any response without requiring authentication, the authentication bypass vulnerability is present
  4. Determine if jk-status endpoint is exposed
    Attempt to access the /jk-status Web-UI endpoint on your PAM server (typically via HTTP/HTTPS on the management port) without providing credentials
    Affected if The endpoint is accessible and returns any response without requiring authentication, the authentication bypass vulnerability is present

Your environment is affected if CA/Broadcom Privileged Access Manager versions 3.0.1-3.0.3, 3.1.1-3.1.2, or 3.2.0-3.2.1 are installed AND the jk-manager or jk-status endpoints are accessible without authentication.

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 a release after 3.2.1
Interim mitigation

Apply available patches from CA/Broadcom for PAM 3.x and ensure jk-manager and jk-status endpoints require proper authentication or are network-segmented from untrusted networks.

Recommended fix Moderate confidence

CA Privileged Access Manager 3.3.0 or later (contact CA/Broadcom support for exact fixed version)

  1. Identify the currently installed CA Privileged Access Manager version by accessing the product's admin console or checking system information
  2. Determine if the installed version falls within any of the affected ranges: 3.0.1-3.0.3, 3.1.1-3.1.2, or 3.2.0-3.2.1
  3. Download the latest available version of CA Privileged Access Manager from the official CA Technologies/Broadcom support portal
  4. Plan an upgrade window and review upgrade documentation for your current version
  5. Execute the upgrade following the official CA PAM upgrade procedure
  6. After upgrade, verify the jk-manager and jk-status components are functioning correctly and accessible only with proper authentication
  7. Validate that the vulnerability is resolved by attempting unauthorized access to the affected endpoints
Caveat Review CA/Broadcom release notes for your specific version upgrade path as configuration changes between major.minor versions may require migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Privileged Access Manager 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 the upgrade done

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-2019-7392 — 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-2019-7392 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