CVE-2019-3760
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 software and RSA Via Lifecycle and Governance products prior to 7.1.0 P08 contain a SQL Injection vulnerability in Workflow Architect. A remote authenticated malicious user could potentially exploit this vulnerability to execute SQL commands on the back-end database to gain unauthorized access to the data by supplying specially crafted input data to the affected 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 confidenceSQL injection vulnerability in the Workflow Architect component of RSA Identity Governance and Lifecycle and RSA Via Lifecycle and Governance products. A remote authenticated attacker can exploit specially crafted input to execute arbitrary SQL commands on the backend database, potentially exposing or manipulating sensitive data.
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.1= 7.0.2= 7.1.0= 7.1.1= 7.0.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 RSA product versionAccess the administration console or check the product UI help/about section. The version is typically displayed in the system information or about page. Alternatively, check the installation directory for a version file or query the database for version metadata.Affected if The installed version matches 7.0.1, 7.0.2, 7.1.0, 7.1.1 for Identity Governance and Lifecycle, or 7.0.0 for Via Lifecycle and Governance
-
Verify Workflow Architect component is accessibleLog into the RSA governance portal and navigate to the Workflow Architect feature. This is typically found under the Workflows or Designer section in the web interface. Confirm the component loads and is functional for the authenticated user.Affected if The Workflow Architect component is available and accessible to the authenticated user
-
Check for anomalous SQL behavior in Workflow ArchitectMonitor database query logs or web application logs while using the Workflow Architect. Look for unusual or unexpected SQL query patterns, especially those containing SQL operators or commands that could indicate injection attempts.Affected if Unusual SQL patterns appear in logs when the Workflow Architect processes input, suggesting the vulnerability may be present
You are affected if you are running version 7.0.1, 7.0.2, 7.1.0, or 7.1.1 of RSA Identity Governance and Lifecycle, or version 7.0.0 of RSA Via Lifecycle and Governance, and the Workflow Architect component is accessible to authenticated users.
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 RSA Identity Governance and Lifecycle or RSA Via Lifecycle and Governance version 7.1.0 P08 or later. Apply input validation and parameterized queries as defense-in-depth measures.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3760 — 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-3760 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