CVE-2019-18573
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 a Session Fixation vulnerability. An authenticated malicious local user could potentially exploit this vulnerability as the session token is exposed as part of the URL. A remote attacker can gain access to victim’s session and perform arbitrary actions with privileges of the user within the compromised session.
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 confidenceThis is a Session Fixation vulnerability in RSA Identity Governance and Lifecycle products where the session token is exposed in the URL rather than stored in secure HTTP-only cookies. An authenticated attacker can exploit this by obtaining or predicting the session ID from the URL and hijacking the user's session to perform privileged actions.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 product versionCheck the version of RSA Identity Governance and Lifecycle installed in your environment. This is typically visible in the product's about page, system information, or by querying the application server's version information.Affected if Version matches 7.0, 7.0.1, 7.0.2, 7.1.0, or 7.1.1
-
Verify session token placement in URLLog into the RSA Identity Governance and Lifecycle web interface using a browser. After authentication, examine the browser's address bar and look for a session identifier, session token, or similar parameter in the URL (for example, a parameter containing a long alphanumeric string).Affected if Any session-related identifier appears in the URL after login instead of being managed transparently through cookies
-
Check for HTTP-only session cookiesOpen the browser's developer tools (F12), go to the Application or Storage tab, and inspect cookies for the application domain. Verify whether the session cookie exists and whether it has the HttpOnly and Secure flags set.Affected if No HTTP-only session cookie exists, or session tokens are transmitted via URL rather than cookies
-
Inspect HTTP headers for session managementUse the Network tab in browser developer tools to capture HTTP requests and responses during login and subsequent navigation. Examine the Set-Cookie headers to determine how session identifiers are being handled.Affected if Session IDs are returned in URL parameters or non-HTTP-only cookies rather than in HTTP-only secure cookies
A user is affected if their installed version falls within 7.0 through 7.1.1 and session identifiers are observable in browser URLs after authentication instead of being managed exclusively through HTTP-only cookies.
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 dataUpgrade to version 7.1.1 P03 or later which implements secure session management using HTTP-only cookies instead of URL-based session tokens.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18573 — 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-18573 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