# CVE-2015-1849: Information disclosure in n/a > Attackers can obtain sensitive LDAP credentials from logs when TRACE logging is enabled in JBoss EAP. - **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Sep 2017 - **Updated:** 6 Aug 2024 - **Also known as:** GHSA-6hhx-86qx-9ffc, RHBA-2015:1073, RHEA-2015:1074, RHEA-2015:1075, RHEA-2015:1076 ## What is CVE-2015-1849? CVE-2015-1849 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 19 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description AdvancedLdapLodinMogule in Red Hat JBoss Enterprise Application Platform (EAP) before 6.4.1 allows attackers to obtain sensitive information via vectors involving logging the LDAP bind credential password when TRACE logging is enabled. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2015-1849? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `jboss-as-appclient` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-cli` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-client-all` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-clustering` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-cmp` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-configadmin` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-connector` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-controller` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-controller-client` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-core-security` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-deployment-repository` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-deployment-scanner` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-domain-http` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-domain-management` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-ee` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-ee-deployment` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-ejb3` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-embedded` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-host-controller` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-jacorb` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-jaxr` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-jaxrs` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-jdr` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-jmx` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-jpa` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-jsf` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-jsr77` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-logging` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-mail` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-management-client-content` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-messaging` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-modcluster` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-naming` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-network` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-osgi` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-osgi-configadmin` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-osgi-service` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-picketlink` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-platform-mbean` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | | `jboss-as-pojo` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.1-3.Final_redhat_3.1.ep6.el5 | Products: Redhat Jboss Enterprise Application Platform. ## How do I fix CVE-2015-1849? Upgrade to a fixed version. ## Is CVE-2015-1849 being exploited? There is no known exploitation of CVE-2015-1849 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-2015-1849 and fix it if it is affected. What it is: CVE-2015-1849 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 19 Sep 2017. 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-2015-1849 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-2015-1849/ (Markdown: https://insights.sbomify.com/CVE-2015-1849/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2015-1849 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-1849 - OSV: https://osv.dev/vulnerability/CVE-2015-1849 --- From sbomify Insights: https://insights.sbomify.com/CVE-2015-1849/ Summaries are generated and may contain mistakes; the official description above is the record.