# CVE-2020-4584: Information disclosure in i2 iBase

> Remote attackers can obtain sensitive information via detailed technical error messages in IBM i2 iBase, aiding further attacks.

- **Severity:** Low 3.3 (`CVSS:3.0/C:L/AV:L/AC:L/A:N/S:U/I:N/UI:N/PR:L/RL:O/RC:C/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-893j-mp6c-6pj8

## What is CVE-2020-4584?

CVE-2020-4584 is a low-severity vulnerability in IBM i2 iBase, published on 30 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM i2 iBase 8.9.13 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system. IBM X-Force ID: 184574.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2020-4584?

It affects 1 product.


Products: Ibm I2 Ibase.

## How do I fix CVE-2020-4584?

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

## Is CVE-2020-4584 being exploited?

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

## Other vulnerabilities in IBM i2 iBase

- [CVE-2020-4623](https://insights.sbomify.com/CVE-2020-4623/): Other in i2 iBase (high 7.7)
- [CVE-2020-4588](https://insights.sbomify.com/CVE-2020-4588/): File upload in i2 iBase (high 7.7)
- [CVE-2021-29868](https://insights.sbomify.com/CVE-2021-29868/): Information disclosure in i2 iBase (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-4584 and fix it if it is affected.

What it is: CVE-2020-4584 is a low-severity vulnerability in IBM i2 iBase, published on 30 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-4584 in the wild and no public exploit code.

Affected product: IBM i2 iBase. 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-2020-4584/ (Markdown: https://insights.sbomify.com/CVE-2020-4584/index.md)
```

## Sources

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

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