# CVE-2020-25680: Security feature bypass in JBCS httpd

> JBCS httpd fails to validate backend SSL certificate hostnames, allowing attackers to bypass security checks and compromise data integrity.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h32x-w4cv-wrq9

## What is CVE-2020-25680?

CVE-2020-25680 is a medium-severity vulnerability in JBCS httpd, published on 7 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in JBCS httpd in version 2.4.37 SP3, where it uses a back-end worker SSL certificate with the keystore file's ID is 'unknown'. The validation of the certificate whether CN and hostname are matching stopped working and allow connecting to the back-end work. The highest threat from this vulnerability is to data integrity.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Redhat Jboss Core Services Httpd.

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

Apply the vendor's patch.

## Is CVE-2020-25680 being exploited?

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

## Other vulnerabilities in JBCS httpd

- [CVE-2021-3688](https://insights.sbomify.com/CVE-2021-3688/): Path traversal in Red Hat JBCS HTTP Server (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25680 is a medium-severity vulnerability in JBCS httpd, published on 7 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-25680 in the wild and no public exploit code.

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

## Sources

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

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