CVE-2019-18572
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 · uneditedThe RSA Identity Governance and Lifecycle and RSA Via Lifecycle and Governance products prior to 7.1.1 P03 contain an Improper Authentication vulnerability. A Java JMX agent running on the remote host is configured with plain text password authentication. An unauthenticated remote attacker can connect to the JMX agent and monitor and manage the Java application.
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 confidenceRSA Identity Governance and Lifecycle products contain a Java JMX agent configured with plain text password authentication, allowing unauthenticated remote attackers to connect and fully manage the Java application due to improper authentication controls.
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= 7.0= 7.0.1= 7.0.2= 7.1.0= 7.1.1CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify installed versionCheck the product version through the administrative console or by querying the installed software package. This is typically visible in the product UI under About or System Information, or can be obtained via command line tools used for the installation.Affected if The installed version matches 7.0, 7.0.1, 7.0.2, 7.1.0, or 7.1.1 exactly.
-
Determine if JMX service is enabledInspect the Java application server configuration files and running processes to identify whether the Java Management Extensions (JMX) agent is actively running. Look for JMX-related service configurations or port listeners commonly associated with JMX.Affected if JMX is enabled and listening on a network port accessible from remote systems.
-
Verify JMX authentication configurationExamine the JMX configuration files for the authentication settings. Check whether the JMX connector is configured with authentication enabled and whether credentials are stored in plain text.Affected if JMX is configured with authentication using plain text passwords, allowing remote connections without proper encrypted credential storage.
-
Assess network accessibility of JMX portDetermine if the JMX port is exposed to network-accessible interfaces rather than bound only to localhost. Review firewall rules and service binding configurations.Affected if The JMX service is bound to a publicly accessible network interface and accepts remote connections.
The environment is affected if the installed version is exactly 7.0, 7.0.1, 7.0.2, 7.1.0, or 7.1.1 AND the JMX agent is enabled with plain text password authentication accessible from remote networks.
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 dataApply vendor patch 7.1.1 P03 or later to address the improper authentication vulnerability. If JMX is not required, consider disabling it or implementing proper authentication with encrypted credentials.
- Consultation4.0 h
- Implementation3.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18572 — 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-18572 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