# CVE-2018-1245: Authorization ByPass Vulnerability

> Authenticated non-admin users can bypass Java Security Policies to execute arbitrary OS commands with application owner privileges.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-j3hm-2gx9-6x67

## What is CVE-2018-1245?

CVE-2018-1245 is a critical authentication bypass vulnerability in RSA Identity Governance and Lifecycle, published on 13 Jul 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

RSA 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2018-1245?

It affects 1 product.


Products: Emc Rsa Identity Governance and Lifecycle.

## How do I fix CVE-2018-1245?

No fix has been published for CVE-2018-1245 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-1245 being exploited?

There is no known exploitation of CVE-2018-1245 in the wild and no public exploit code.

## Other vulnerabilities in RSA Identity Governance and Lifecycle

- [CVE-2018-1182](https://insights.sbomify.com/CVE-2018-1182/): Privilege escalation in EMC RSA Identity Governance and Lifecycle versions 7.0.1, 7.0.2, all patch levels (hardware appliance and software bundle deployments only); RSA Via Lifecycle and Governance version 7.0, all patch levels (hardware appliance and software bundle deployments only); RSA Identity Management & Governance (RSA IMG) versions 6.9.0, 6.9.1, all patch levels (hardware appliance and software bundle deployments only) (high 7.8)
- [CVE-2018-11049](https://insights.sbomify.com/CVE-2018-11049/): RSA Identity Governance and Lifecycle Uncontrolled Search Path Vulnerability (high 7.3)
- [CVE-2017-8004](https://insights.sbomify.com/CVE-2017-8004/): File upload in RSA Identity Governance and Lifecycle, RSA Via Lifecycle and Governance, RSA Identity Management and Governance (RSA IMG) (high 7.2)
- [CVE-2018-1255](https://insights.sbomify.com/CVE-2018-1255/): Reflected Cross-Site Scripting Vulnerability (medium 6.1)
- [CVE-2017-5003](https://insights.sbomify.com/CVE-2017-5003/): Cross-site scripting in RSA Identity Governance and Lifecycle versions 7.0.1, 7.0.2, all patch levels, RSA Via Lifecycle and Governance version 7.0, all patch levels, RSA Identity Management and Governance (RSA IMG) versions 6.9.1, all patch levels (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1245 and fix it if it is affected.

What it is: CVE-2018-1245 is a critical authentication bypass vulnerability in RSA Identity Governance and Lifecycle, published on 13 Jul 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1245 in the wild and no public exploit code.

Affected product: RSA Identity Governance and Lifecycle. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1245/ (Markdown: https://insights.sbomify.com/CVE-2018-1245/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1245
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1245
- OSV: https://osv.dev/vulnerability/CVE-2018-1245

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1245/
Summaries are generated and may contain mistakes; the official description above is the record.