# CVE-2019-14823: Security feature bypass in JSS

> Attackers can bypass certificate chain verification in JSS CryptoManager, enabling Man-in-the-Middle attacks against applications using the vulnerable OCSP policy.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-14823, GHSA-45q2-f3rm-5r6v, MGASA-2020-0018, RHSA-2019:3067, RHSA-2019:3225

## What is CVE-2019-14823?

CVE-2019-14823 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 14 Oct 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw was found in the "Leaf and Chain" OCSP policy implementation in JSS' CryptoManager versions after 4.4.6, 4.5.3, 4.6.0, where it implicitly trusted the root certificate of a certificate chain. Applications using this policy may not properly verify the chain and could be vulnerable to attacks such as Man in the Middle.

Weakness: CWE-295 (Improper Certificate Validation), CWE-358 (Improperly Implemented Security Check for Standard)

## Which versions are affected by CVE-2019-14823?

It affects 8 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jss` | Red Hat:enterprise_linux:7::client | All versions | 0:4.4.6-3.el7_7 |
| `jss-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:4.4.6-3.el7_7 |
| `jss-javadoc` | Red Hat:enterprise_linux:7::client | All versions | 0:4.4.6-3.el7_7 |
| `jss` | Red Hat:enterprise_linux:7::computenode | All versions | 0:4.4.6-3.el7_7 |
| `jss-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:4.4.6-3.el7_7 |
| `jss-javadoc` | Red Hat:enterprise_linux:7::computenode | All versions | 0:4.4.6-3.el7_7 |
| `jss` | Red Hat:enterprise_linux:7::server | All versions | 0:4.4.6-3.el7_7 |
| `jss-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:4.4.6-3.el7_7 |
| `jss-javadoc` | Red Hat:enterprise_linux:7::server | All versions | 0:4.4.6-3.el7_7 |
| `jss` | Red Hat:enterprise_linux:7::workstation | All versions | 0:4.4.6-3.el7_7 |
| `jss-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:4.4.6-3.el7_7 |
| `jss-javadoc` | Red Hat:enterprise_linux:7::workstation | All versions | 0:4.4.6-3.el7_7 |
| `jss` | Red Hat:rhel_eus:7.6::computenode | All versions | 0:4.4.4-6.el7_6 |
| `jss-debuginfo` | Red Hat:rhel_eus:7.6::computenode | All versions | 0:4.4.4-6.el7_6 |
| `jss-javadoc` | Red Hat:rhel_eus:7.6::computenode | All versions | 0:4.4.4-6.el7_6 |
| `jss` | Red Hat:rhel_eus:7.6::server | All versions | 0:4.4.4-6.el7_6 |
| `jss-debuginfo` | Red Hat:rhel_eus:7.6::server | All versions | 0:4.4.4-6.el7_6 |
| `jss-javadoc` | Red Hat:rhel_eus:7.6::server | All versions | 0:4.4.4-6.el7_6 |

Products: Jss Cryptomanager Project Jss Cryptomanager, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation.

## How do I fix CVE-2019-14823?

Apply the vendor's patch.

## Is CVE-2019-14823 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14823 and fix it if it is affected.

What it is: CVE-2019-14823 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 14 Oct 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-14823 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. 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-2019-14823/ (Markdown: https://insights.sbomify.com/CVE-2019-14823/index.md)
```

## Sources

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

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