# CVE-2018-3048: Missing authorization in Banking Corporate Lending

> Low-privileged attackers can modify or read banking data via HTTP with user interaction, requiring patches for Oracle Banking Corporate Lending.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **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 Jul 2018
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-226r-7mhp-678g

## What is CVE-2018-3048?

CVE-2018-3048 is a medium-severity missing authorization vulnerability in Oracle Corporation Banking Corporate Lending, published on 18 Jul 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 Banking Corporate Lending component of Oracle Financial Services Applications (subcomponent: Core module). Supported versions that are affected are 12.3.0, 12.4.0, 12.5.0, 14.0.0 and 14.1.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Banking Corporate Lending. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Banking Corporate Lending, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Banking Corporate Lending accessible data as well as unauthorized read access to a subset of Oracle Banking Corporate Lending accessible data. CVSS 3.0 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).

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

It affects 1 product.


Products: Oracle Banking Corporate Lending.

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

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

## Is CVE-2018-3048 being exploited?

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

## Other vulnerabilities in Oracle Corporation Banking Corporate Lending

- [CVE-2018-2706](https://insights.sbomify.com/CVE-2018-2706/): Auth bypass in Banking Corporate Lending (high 8.8)
- [CVE-2018-3050](https://insights.sbomify.com/CVE-2018-3050/): Missing authorization in Banking Corporate Lending (high 8.1)
- [CVE-2018-2707](https://insights.sbomify.com/CVE-2018-2707/): Missing authorization in Banking Corporate Lending (high 8.1)
- [CVE-2020-2718](https://insights.sbomify.com/CVE-2020-2718/): Missing authorization in Banking Corporate Lending (high 7.1)
- [CVE-2018-2746](https://insights.sbomify.com/CVE-2018-2746/): Information disclosure in FLEXCUBE Universal Banking (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-3048 is a medium-severity missing authorization vulnerability in Oracle Corporation Banking Corporate Lending, published on 18 Jul 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-3048 in the wild and no public exploit code.

Affected product: Oracle Corporation Banking Corporate Lending. 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-3048/ (Markdown: https://insights.sbomify.com/CVE-2018-3048/index.md)
```

## Sources

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

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