CVE-2018-1245
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 · uneditedRSA Identity Lifecycle and Governance versions 7.0.1, 7.0.2 and 7.1.0 contains an authorization bypass vulnerability within the workflow architect component (ACM). A remote authenticated malicious user with non-admin privileges could potentially bypass the Java Security Policies. Once bypassed, a malicious user could potentially run arbitrary system commands at the OS level with application owner privileges on the affected system.
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 Lifecycle and Governance contains an authorization bypass in the workflow architect component (ACM). An authenticated non-admin user can bypass Java Security Policies, enabling execution of arbitrary operating system commands with application owner privileges. This is a privilege escalation and code execution vulnerability requiring only standard user authentication.
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.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.0/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 Identity Governance and Lifecycle versionLocate the version information for the RSA Identity Governance and Lifecycle installation using the system's standard version check mechanism (typically accessible via admin console, about page, or version file)Affected if The installed version is 7.0.1, 7.0.2, or 7.1.0
-
Confirm workflow architect (ACM) component is accessibleCheck whether the ACM (workflow architect) component is available and exposed to standard user accounts in the RSA applicationAffected if Non-admin user accounts can access or log into the workflow architect component
-
Verify user role configuration for ACM accessReview the user role assignments and permissions configuration to determine whether non-administrative users have been granted access to the workflow architect moduleAffected if Standard or non-admin users have explicit or inherited access permissions to the ACM component
-
Audit for suspicious command executionReview application logs, system logs, and audit trails for unexpected or unauthorized operating system commands executed from the application service account context, particularly commands originating from workflow-related operationsAffected if Unusual OS-level commands appear in logs executed with application owner privileges, especially from non-admin user sessions
The environment is affected if running version 7.0.1, 7.0.2, or 7.1.0 AND non-admin users have access to the workflow architect (ACM) component, or if evidence of unauthorized command execution exists in logs.
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 patches for CVE-2018-1245 when available. Until patched, restrict access to the workflow architect component to admin-only users and implement network segmentation to limit exposure. Monitor for suspicious command execution from application service accounts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2018-1245 — 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-2018-1245 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