# CVE-2021-2110: Information disclosure in Argus Safety

> Low-privileged attackers can exploit this vulnerability to gain unauthorized read access to a subset of data in Oracle Argus Safety.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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:** 20 Jan 2021
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-9p74-pqx9-3mrw

## What is CVE-2021-2110?

CVE-2021-2110 is a medium-severity vulnerability in Oracle Corporation Argus Safety, published on 20 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Oracle Argus Safety product of Oracle Health Sciences Applications (component: Letters). The supported version that is affected is 8.2.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Argus Safety. While the vulnerability is in Oracle Argus Safety, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Argus Safety accessible data. CVSS 3.1 Base Score 5.0 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N).

## Which versions are affected by CVE-2021-2110?

It affects 1 product.


Products: Oracle Argus Safety.

## How do I fix CVE-2021-2110?

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

## Is CVE-2021-2110 being exploited?

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

## Other vulnerabilities in Oracle Corporation Argus Safety

- [CVE-2018-2613](https://insights.sbomify.com/CVE-2018-2613/): Auth bypass in Argus Safety (high 8.2)
- [CVE-2010-3593](https://insights.sbomify.com/CVE-2010-3593/): Auth bypass in n/a (high 7.5)
- [CVE-2019-2430](https://insights.sbomify.com/CVE-2019-2430/): Information disclosure in Argus Safety (medium 6.5)
- [CVE-2018-2642](https://insights.sbomify.com/CVE-2018-2642/): File upload in Argus Safety (medium 6.5)
- [CVE-2018-2643](https://insights.sbomify.com/CVE-2018-2643/): Missing authorization in Argus Safety (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-2110 and fix it if it is affected.

What it is: CVE-2021-2110 is a medium-severity vulnerability in Oracle Corporation Argus Safety, published on 20 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-2110 in the wild and no public exploit code.

Affected product: Oracle Corporation Argus Safety. 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-2021-2110/ (Markdown: https://insights.sbomify.com/CVE-2021-2110/index.md)
```

## Sources

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

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