# CVE-2020-14204: In WebFOCUS Business Intelligence 8.0 (SP6), the administration portal allows remote attackers to read arbitrary local files or forge server


- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2r5q-g9p8-3977

## What is CVE-2020-14204?

CVE-2020-14204 is a high-severity vulnerability in n/a, published on 22 Jun 2020. 

### Official description

In WebFOCUS Business Intelligence 8.0 (SP6), the administration portal allows remote attackers to read arbitrary local files or forge server-side HTTP requests via a crafted HTTP request to /ibi_apps/WFServlet.cfg because XML external entity injection is possible. This is related to making changes to the application repository configuration.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

It affects 1 product.


Products: Ibi Webfocus Business Intelligence.

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

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

## Is CVE-2020-14204 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-14203](https://insights.sbomify.com/CVE-2020-14203/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-14202](https://insights.sbomify.com/CVE-2020-14202/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-14204 is a high-severity vulnerability in n/a, published on 22 Jun 2020. 
Exploitation: There is no known exploitation of CVE-2020-14204 in the wild and no public exploit code.

Affected product: n/a. 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-14204/ (Markdown: https://insights.sbomify.com/CVE-2020-14204/index.md)
```

## Sources

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

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