# CVE-2020-25256: Hardcoded credentials in n/a

> Hyland OnBase uses identical private keys for PKI certificates across installations, allowing attackers to decrypt data or bypass security controls.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9xgq-hv63-rmpj

## What is CVE-2020-25256?

CVE-2020-25256 is a critical vulnerability in n/a, published on 11 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Hyland OnBase 16.0.2.83 and below, 17.0.2.109 and below, 18.0.0.37 and below, 19.8.16.1000 and below and 20.3.10.1000 and below. PKI certificates have a private key that is the same across different customers' installations.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Hyland Onbase.

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

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

## Is CVE-2020-25256 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-25253](https://insights.sbomify.com/CVE-2020-25253/): SQL injection in n/a (critical 9.8)
- [CVE-2020-25254](https://insights.sbomify.com/CVE-2020-25254/): SQL injection in n/a (critical 9.8)
- [CVE-2020-25257](https://insights.sbomify.com/CVE-2020-25257/): XML external entity in n/a (critical 9.8)
- [CVE-2020-25258](https://insights.sbomify.com/CVE-2020-25258/): Deserialization in n/a (critical 9.8)
- [CVE-2020-25259](https://insights.sbomify.com/CVE-2020-25259/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25256 is a critical vulnerability in n/a, published on 11 Sep 2020. 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-2020-25256 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-25256/ (Markdown: https://insights.sbomify.com/CVE-2020-25256/index.md)
```

## Sources

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

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