# CVE-2019-14885: Information disclosure in JBoss EAP

> Attackers can read confidential security attribute values from JBoss EAP log files after a reload command, exposing sensitive system properties.

- **Severity:** Medium 5.4 (`CVSS:3.0/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:** 23 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cxpp-v3rm-fq33, RHSA-2020:2169

## What is CVE-2019-14885?

CVE-2019-14885 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 23 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the JBoss EAP Vault system in all versions before 7.2.6.GA. Confidential information of the system property's security attribute value is revealed in the JBoss EAP log file when executing a JBoss CLI 'reload' command. This flaw can lead to the exposure of confidential information.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jboss-as-controller` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.22-3.Final_redhat_4.1.ep6.el5 |
| `jboss-as-server` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.22-3.Final_redhat_4.1.ep6.el5 |
| `jboss-as-weld` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.22-3.Final_redhat_4.1.ep6.el5 |
| `jboss-as-controller` | Red Hat:jboss_enterprise_application_platform:6::el6 | All versions | 0:7.5.22-3.Final_redhat_4.1.ep6.el6 |
| `jboss-as-server` | Red Hat:jboss_enterprise_application_platform:6::el6 | All versions | 0:7.5.22-3.Final_redhat_4.1.ep6.el6 |
| `jboss-as-weld` | Red Hat:jboss_enterprise_application_platform:6::el6 | All versions | 0:7.5.22-3.Final_redhat_4.1.ep6.el6 |
| `jboss-as-controller` | Red Hat:jboss_enterprise_application_platform:6::el7 | All versions | 0:7.5.22-3.Final_redhat_4.1.ep6.el7 |
| `jboss-as-server` | Red Hat:jboss_enterprise_application_platform:6::el7 | All versions | 0:7.5.22-3.Final_redhat_4.1.ep6.el7 |
| `jboss-as-weld` | Red Hat:jboss_enterprise_application_platform:6::el7 | All versions | 0:7.5.22-3.Final_redhat_4.1.ep6.el7 |

Products: Redhat Jboss Enterprise Application Platform, Redhat Single Sign-On.

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

Upgrade to a fixed version.

## Is CVE-2019-14885 being exploited?

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

## Other vulnerabilities in Redhat Jboss Enterprise Application Platform

- [CVE-2017-12149](https://insights.sbomify.com/CVE-2017-12149/): Red Hat JBoss Application Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2010-1428](https://insights.sbomify.com/CVE-2010-1428/): Red Hat JBoss Information Disclosure (medium 5.9, exploited in the wild)
- [CVE-2010-0738](https://insights.sbomify.com/CVE-2010-0738/): Red Hat JBoss Authentication Bypass (low 3.7, exploited in the wild)
- [CVE-2016-3690](https://insights.sbomify.com/CVE-2016-3690/): Deserialization in n/a (critical 9.8)
- [CVE-2017-7504](https://insights.sbomify.com/CVE-2017-7504/): Deserialization in JBoss (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14885 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 23 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-14885 in the wild and no public exploit code.

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

## Sources

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

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