# CVE-2022-26949: Missing authorization in n/a

> Remote authenticated users can access restricted attachment files due to improper access control in Archer GRC.

- **Severity:** Medium 5.3 (`CVSS:3.1/AC:H/AV:N/A:N/C:H/I:N/PR:L/S:U/UI: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:** 29 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6j44-3gp8-rfhg

## What is CVE-2022-26949?

CVE-2022-26949 is a medium-severity missing authorization vulnerability in n/a, published on 29 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Archer 6.x through 6.9 SP2 P1 (6.9.2.1) contains an improper access control vulnerability on attachments. A remote authenticated malicious user could potentially exploit this vulnerability to gain access to files that should only be allowed by extra privileges.

## Which versions are affected by CVE-2022-26949?

It affects 1 product.


Products: Rsa Archer.

## How do I fix CVE-2022-26949?

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

## Is CVE-2022-26949 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-30584](https://insights.sbomify.com/CVE-2022-30584/): Missing authorization in n/a (critical 9.6)
- [CVE-2020-5331](https://insights.sbomify.com/CVE-2020-5331/): Information disclosure in RSA Archer (high 8.8)
- [CVE-2018-11060](https://insights.sbomify.com/CVE-2018-11060/): Privilege escalation in RSA Archer (high 8.8)
- [CVE-2020-5334](https://insights.sbomify.com/CVE-2020-5334/): Cross-site scripting in RSA Archer (high 8.2)
- [CVE-2018-11059](https://insights.sbomify.com/CVE-2018-11059/): Cross-site scripting in RSA Archer (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26949 and fix it if it is affected.

What it is: CVE-2022-26949 is a medium-severity missing authorization vulnerability in n/a, published on 29 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-26949 in the wild and no public exploit code.

Affected product: n/a. 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-2022-26949/ (Markdown: https://insights.sbomify.com/CVE-2022-26949/index.md)
```

## Sources

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

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