# CVE-2018-2642: File upload in Argus Safety

> Low-privileged attackers can exploit a file upload vulnerability in Oracle Argus Safety to read, modify, or delete data and cause partial denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **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:** 18 Jan 2018
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-857j-69r5-fpw7

## What is CVE-2018-2642?

CVE-2018-2642 is a medium-severity vulnerability in Oracle Corporation Argus Safety, published on 18 Jan 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

Vulnerability in the Oracle Argus Safety component of Oracle Health Sciences Applications (subcomponent: File Upload). Supported versions that are affected are 7.x and 8.0.x. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Argus Safety. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Argus Safety, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Argus Safety accessible data as well as unauthorized read access to a subset of Oracle Argus Safety accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Argus Safety. CVSS 3.0 Base Score 6.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L).

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

It affects 1 product.


Products: Oracle Argus Safety.

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

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

## Is CVE-2018-2642 being exploited?

There is no known exploitation of CVE-2018-2642 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-2643](https://insights.sbomify.com/CVE-2018-2643/): Missing authorization in Argus Safety (medium 6.4)
- [CVE-2025-21570](https://insights.sbomify.com/CVE-2025-21570/): Missing authorization in Oracle Life Sciences Argus Safety (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-2642 is a medium-severity vulnerability in Oracle Corporation Argus Safety, published on 18 Jan 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-2642 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-2018-2642/ (Markdown: https://insights.sbomify.com/CVE-2018-2642/index.md)
```

## Sources

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

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