dbcve.org
Rsa Identity Governance And LifecycleApplication · Dell

CVE-2019-3761

MEDIUM · 5.4 CVSS v3.1 Published 2019-09-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The RSA Identity Governance and Lifecycle software and RSA Via Lifecycle and Governance products prior to 7.1.0 P08 contain a stored cross-site scripting vulnerability in the Access Request module. A remote authenticated malicious user could potentially exploit this vulnerability to store malicious HTML or JavaScript code in a trusted application data store. When victim users access the data store through their browsers, the stored malicious code would gets executed by the web browser in the context of the vulnerable web 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 confidence

A stored cross-site scripting (XSS) vulnerability in the Access Request module of RSA Identity Governance and Lifecycle and RSA Via Lifecycle and Governance products allows authenticated users to inject malicious HTML or JavaScript code into the application's data store. When other users view this data through their browsers, the injected code executes within the context of the trusted web application.

MitigationUpgrade to RSA Identity Governance and Lifecycle or RSA Via Lifecycle and Governance version 7.1.0 P08 or later, which contains the vendor patch for this vulnerability. Additionally, implement output encoding and input validation on the Access Request module as compensating controls until the patch can be applied.

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
Rsa Identity Governance And LifecycleApplication
Affected:= 7.0.1= 7.0.2= 7.1.0= 7.1.1
Rsa Via Lifecycle And GovernanceApplication
Affected:= 7.0.0

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Identify the installed RSA Identity Governance and Lifecycle or RSA Via Lifecycle and Governance version
    Access the product's administrative console or check the system information page. Typically found under Help > About or System > Settings > System Information. The version number is displayed prominently.
    Affected if The installed version is 7.0.0, 7.0.1, 7.0.2, 7.1.0, or 7.1.1.
  2. Confirm the Access Request module is accessible
    Log into the web application as a standard user and navigate to the Access Request section. Verify the module loads and accepts user input for access requests.
    Affected if The Access Request module is enabled and users can submit access requests.
  3. Review Access Request data for suspicious content
    Using an administrative account, query the Access Request database or export access request records. Look for entries containing HTML tags, script elements, or JavaScript event handlers in request fields such as justification, description, or custom attributes.
    Affected if Stored entries in Access Request contain unescaped HTML, script tags, or JavaScript code that would execute when viewed.

You are affected if you are running version 7.0.0 through 7.1.1 and the Access Request module is enabled, allowing users to input data that could be rendered as executable code.

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

Upgrade to RSA Identity Governance and Lifecycle or RSA Via Lifecycle and Governance version 7.1.0 P08 or later, which contains the vendor patch for this vulnerability. Additionally, implement output encoding and input validation on the Access Request module as compensating controls until the patch can be applied.

Fix this in Rsa Identity Governance And Lifecycle Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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