# CVE-2009-0027: Path traversal in n/a > Remote attackers can read arbitrary XML files from the server via a crafted WSDL request in JBossWS. - **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** 9 Mar 2009 - **Updated:** 7 Aug 2024 - **Also known as:** GHSA-5xfj-v547-vccj, RHSA-2009:0346, RHSA-2009:0347, RHSA-2009:0348, RHSA-2009:0349 ## What is CVE-2009-0027? CVE-2009-0027 is a medium-severity path traversal vulnerability in Redhat Jboss Enterprise Application Platform, published on 9 Mar 2009. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The request handler in JBossWS in JBoss Enterprise Application Platform (aka JBoss EAP or JBEAP) 4.2 before 4.2.0.CP06 and 4.3 before 4.3.0.CP04 does not properly validate the resource path during a request for a WSDL file with a custom web-service endpoint, which allows remote attackers to read arbitrary XML files via a crafted request. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2009-0027? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `glassfish-jsf` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:1.2_10-0jpp.ep1.5.ep5.el4 | | `hibernate3` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 1:3.2.4-1.SP1_CP07.0jpp.ep1.14.el4 | | `hibernate3-javadoc` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 1:3.2.4-1.SP1_CP07.0jpp.ep1.14.el4 | | `jacorb` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:2.3.0-1jpp.ep1.7.el4 | | `jakarta-commons-fileupload` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 1:1.1.1-3jpp.ep1.2.el4 | | `jakarta-commons-io` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:1.1-0.20051005.2jpp_1rh | | `jakarta-commons-logging-jboss` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:1.1-4.ep1.el4 | | `jboss-cache` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:1.4.1-6.SP11.1.ep1.el4 | | `jboss-jaxr` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:1.2.0-SP2.0jpp.ep1.3.el4 | | `jboss-remoting` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:2.2.2-3.SP11.0jpp.ep1.1.el4 | | `jboss-seam` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:1.2.1-1.ep1.18.el4 | | `jboss-seam-docs` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:1.2.1-1.ep1.18.el4 | | `jboss-vfs` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:1.0.0-1.ep1.el4 | | `jbossas` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:4.2.0-4.GA_CP06.3.ep1.el4 | | `jbossas-4.2.0.GA_CP06-bin` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:4.2.0-4.GA_CP06.3.ep1.el4 | | `jbossas-client` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:4.2.0-4.GA_CP06.3.ep1.el4 | | `jbossts` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 1:4.2.3-1.SP5_CP04.1jpp.ep1.1.el4 | | `jbossweb` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:2.0.0-6.CP09.0jpp.ep1.1.el4 | | `jgroups` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 1:2.4.5-2.ep1.el4 | | `rh-eap-docs` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:4.2.0-5.GA_CP06.ep1.3.el4 | | `rh-eap-docs-examples` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:4.2.0-5.GA_CP06.ep1.3.el4 | | `tanukiwrapper` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:3.2.1-2jpp.ep1.2.el4 | | `tanukiwrapper-debuginfo` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:3.2.1-2jpp.ep1.2.el4 | | `ws-commons-policy` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:1.0-2jpp.ep1.7.el4 | | `ws-scout0` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:0.7-0.rc2.4.el4 | | `xalan-j2` | Red Hat:jboss_enterprise_application_platform:4.2.0::el4 | All versions | 0:2.7.0-2jpp.ep1.5.el4 | | `glassfish-jsf` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 0:1.2_10-0jpp.ep1.5.ep5.el5 | | `hibernate3` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 1:3.2.4-1.SP1_CP07.0jpp.ep1.14.1.el5 | | `hibernate3-javadoc` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 1:3.2.4-1.SP1_CP07.0jpp.ep1.14.1.el5 | | `jacorb` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 0:2.3.0-1jpp.ep1.7.1.el5 | | `jakarta-commons-logging-jboss` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 0:1.1-4.1.ep1.el5 | | `jboss-cache` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 0:1.4.1-6.SP11.1.ep1.el5 | | `jboss-jaxr` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 0:1.2.0-SP2.0jpp.ep1.3.2.el5 | | `jboss-remoting` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 0:2.2.2-3.SP11.0jpp.ep1.1.el5 | | `jboss-seam` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 0:1.2.1-1.ep1.12.el5 | | `jboss-seam-docs` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 0:1.2.1-1.ep1.12.el5 | | `jboss-vfs` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 0:1.0.0-1.ep1.el5 | | `jbossas` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 0:4.2.0-4.GA_CP06.3.1.ep1.el5 | | `jbossas-4.2.0.GA_CP06-bin` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 0:4.2.0-4.GA_CP06.3.1.ep1.el5 | | `jbossas-client` | Red Hat:jboss_enterprise_application_platform:4.2.0::el5 | All versions | 0:4.2.0-4.GA_CP06.3.1.ep1.el5 | Products: Redhat Jboss Enterprise Application Platform. ## How do I fix CVE-2009-0027? Upgrade to a fixed version. ## Is CVE-2009-0027 being exploited? There is no known exploitation of CVE-2009-0027 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-2009-0027 and fix it if it is affected. What it is: CVE-2009-0027 is a medium-severity path traversal vulnerability in Redhat Jboss Enterprise Application Platform, published on 9 Mar 2009. 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-2009-0027 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-2009-0027/ (Markdown: https://insights.sbomify.com/CVE-2009-0027/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2009-0027 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-0027 - OSV: https://osv.dev/vulnerability/CVE-2009-0027 --- From sbomify Insights: https://insights.sbomify.com/CVE-2009-0027/ Summaries are generated and may contain mistakes; the official description above is the record.