# CVE-2014-0059: Information disclosure in n/a

> Local attackers can read sensitive information from world-readable audit logs in JBoss EAP, requiring an upgrade to secure permissions.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h9mr-9rp7-76qj, RHSA-2014:0563, RHSA-2014:0564

## What is CVE-2014-0059?

CVE-2014-0059 is a low-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 17 Nov 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

JBoss SX and PicketBox, as used in Red Hat JBoss Enterprise Application Platform (EAP) before 6.2.3, use world-readable permissions on audit.log, which allows local users to obtain sensitive information by reading this file.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2014-0059?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glassfish-jsf-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:2.1.28-2.redhat_3.1.ep6.el5 |
| `glassfish-jsf12-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.2_15-7.b01_redhat_11.1.ep6.el5 |
| `hibernate4-core-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.7-8.SP4_redhat_1.1.ep6.el5 |
| `hibernate4-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.7-8.SP4_redhat_1.1.ep6.el5 |
| `hibernate4-entitymanager-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.7-8.SP4_redhat_1.1.ep6.el5 |
| `hibernate4-envers-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.7-8.SP4_redhat_1.1.ep6.el5 |
| `hibernate4-infinispan-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.7-8.SP4_redhat_1.1.ep6.el5 |
| `hornetq` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:2.3.14.1-1.Final_redhat_1.1.ep6.el5 |
| `ironjacamar-common-api-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.23.1-1.Final_redhat_1.1.ep6.el5 |
| `ironjacamar-common-impl-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.23.1-1.Final_redhat_1.1.ep6.el5 |
| `ironjacamar-common-spi-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.23.1-1.Final_redhat_1.1.ep6.el5 |
| `ironjacamar-core-api-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.23.1-1.Final_redhat_1.1.ep6.el5 |
| `ironjacamar-core-impl-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.23.1-1.Final_redhat_1.1.ep6.el5 |
| `ironjacamar-deployers-common-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.23.1-1.Final_redhat_1.1.ep6.el5 |
| `ironjacamar-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.23.1-1.Final_redhat_1.1.ep6.el5 |
| `ironjacamar-jdbc-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.23.1-1.Final_redhat_1.1.ep6.el5 |
| `ironjacamar-spec-api-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.23.1-1.Final_redhat_1.1.ep6.el5 |
| `ironjacamar-validator-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.23.1-1.Final_redhat_1.1.ep6.el5 |
| `jboss-as-appclient` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-cli` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-client-all` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-clustering` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-cmp` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-configadmin` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-connector` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-controller` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-controller-client` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-core-security` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-deployment-repository` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-deployment-scanner` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-domain-http` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-domain-management` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-ee` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-ee-deployment` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-ejb3` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-embedded` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-host-controller` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-jacorb` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-jaxr` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-jaxrs` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.3.3-3.Final_redhat_3.1.ep6.el5 |

Products: Redhat Jboss Enterprise Application Platform.

## How do I fix CVE-2014-0059?

Upgrade to a fixed version.

## Is CVE-2014-0059 being exploited?

There is no known exploitation of CVE-2014-0059 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-2014-0059 and fix it if it is affected.

What it is: CVE-2014-0059 is a low-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 17 Nov 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0059 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-2014-0059/ (Markdown: https://insights.sbomify.com/CVE-2014-0059/index.md)
```

## Sources

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

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