# CVE-2019-2903: Other in Outside In Technology

> Unauthenticated attackers can compromise Oracle Outside In Technology via HTTP, leading to unauthorized data access, modification, and partial denial of service.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2019
- **Updated:** 15 Oct 2024
- **Also known as:** GHSA-q53g-qg59-mcmj

## What is CVE-2019-2903?

CVE-2019-2903 is a high-severity vulnerability in Oracle Outside in Technology, published on 16 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Outside In Technology product of Oracle Fusion Middleware (component: Outside In Filters). The supported version that is affected is 8.5.4. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Outside In Technology. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Outside In Technology accessible data as well as unauthorized read access to a subset of Oracle Outside In Technology accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Outside In Technology. Note: Outside In Technology is a suite of software development kits (SDKs). The protocol and CVSS score depend on the software that uses the Outside In Technology code. The CVSS score assumes that the software passes data received over a network directly to Outside In Technology code, but if data is not received over a network the CVSS score may be lower. CVSS 3.0 Base Score 7.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L).

## Which versions are affected by CVE-2019-2903?

It affects 1 product.


Products: Oracle Outside in Technology.

## How do I fix CVE-2019-2903?

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

## Is CVE-2019-2903 being exploited?

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

## Other vulnerabilities in Oracle Outside in Technology

- [CVE-2015-6013](https://insights.sbomify.com/CVE-2015-6013/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-6014](https://insights.sbomify.com/CVE-2015-6014/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-6015](https://insights.sbomify.com/CVE-2015-6015/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-3266](https://insights.sbomify.com/CVE-2017-3266/): Other in Outside In Technology (critical 9.8)
- [CVE-2021-2066](https://insights.sbomify.com/CVE-2021-2066/): Other in Outside In Technology (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-2903 and fix it if it is affected.

What it is: CVE-2019-2903 is a high-severity vulnerability in Oracle Outside in Technology, published on 16 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-2903 in the wild and no public exploit code.

Affected product: Oracle Outside in Technology. 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-2019-2903/ (Markdown: https://insights.sbomify.com/CVE-2019-2903/index.md)
```

## Sources

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

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