# CVE-2017-4999: Missing authorization in RSA Archer version 5.4.1.3, 5.5.3.1, 5.5.2.3, 5.5.2, 5.5.1.3.1, 5.5.1.1

> A remote low-privileged attacker can bypass authorization in Discussion Forum Messages to view other users' private messages and elevate privileges.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x67m-4j6v-jxhm

## What is CVE-2017-4999?

CVE-2017-4999 is a medium-severity missing authorization vulnerability in RSA Archer version 5.4.1.3, 5.5.3.1, 5.5.2.3, 5.5.2, 5.5.1.3.1, 5.5.1.1, published on 7 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

EMC RSA Archer 5.4.1.3, 5.5.3.1, 5.5.2.3, 5.5.2, 5.5.1.3.1, 5.5.1.1 is affected by an authorization bypass through user-controlled key vulnerability in Discussion Forum Messages. A remote low privileged attacker may potentially exploit this vulnerability to elevate their privileges and view other users' discussion forum messages.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-4999?

It affects 1 product.


Products: Emc Rsa Archer Egrc.

## How do I fix CVE-2017-4999?

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

## Is CVE-2017-4999 being exploited?

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

## Other vulnerabilities in RSA Archer version 5.4.1.3, 5.5.3.1, 5.5.2.3, 5.5.2, 5.5.1.3.1, 5.5.1.1

- [CVE-2017-4998](https://insights.sbomify.com/CVE-2017-4998/): Cross-site request forgery in RSA Archer version 5.4.1.3, 5.5.3.1, 5.5.2.3, 5.5.2, 5.5.1.3.1, 5.5.1.1 (high 8.8)
- [CVE-2012-2292](https://insights.sbomify.com/CVE-2012-2292/): Security feature bypass in n/a (high 7.5)
- [CVE-2015-0542](https://insights.sbomify.com/CVE-2015-0542/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2014-0641](https://insights.sbomify.com/CVE-2014-0641/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2012-2294](https://insights.sbomify.com/CVE-2012-2294/): Other in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-4999 and fix it if it is affected.

What it is: CVE-2017-4999 is a medium-severity missing authorization vulnerability in RSA Archer version 5.4.1.3, 5.5.3.1, 5.5.2.3, 5.5.2, 5.5.1.3.1, 5.5.1.1, published on 7 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-4999 in the wild and no public exploit code.

Affected product: RSA Archer version 5.4.1.3, 5.5.3.1, 5.5.2.3, 5.5.2, 5.5.1.3.1, 5.5.1.1. 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-2017-4999/ (Markdown: https://insights.sbomify.com/CVE-2017-4999/index.md)
```

## Sources

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

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