# CVE-2023-40743: Apache Axis 1.x (EOL) may allow RCE when untrusted input is passed to getService > Attackers can trigger SSRF, DoS, or RCE by passing untrusted input to the getService method in the unsupported Apache Axis 1.x library. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 Sep 2023 - **Updated:** 13 Feb 2025 - **Also known as:** DEBIAN-CVE-2023-40743, DLA-3622-1, GHSA-rmqp-9w4c-gc7w, UBUNTU-CVE-2023-40743, USN-6470-1 ## What is CVE-2023-40743? CVE-2023-40743 is a critical server-side request forgery vulnerability in Apache Axis, published on 5 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description ** UNSUPPORTED WHEN ASSIGNED ** When integrating Apache Axis 1.x in an application, it may not have been obvious that looking up a service through "ServiceFactory.getService" allows potentially dangerous lookup mechanisms such as LDAP. When passing untrusted input to this API method, this could expose the application to DoS, SSRF and even attacks leading to RCE. As Axis 1 has been EOL we recommend you migrate to a different SOAP engine, such as Apache Axis 2/Java. As a workaround, you may review your code to verify no untrusted or unsanitized input is passed to "ServiceFactory.getService", or by applying the patch from https://github.com/apache/axis-axis1-java/commit/7e66753427466590d6def0125e448d2791723210 . The Apache Axis project does not expect to create an Axis 1.x release fixing this problem, though contributors that would like to work towards this are welcome. Weakness: CWE-75 (Failure to Sanitize Special Elements into a Different Plane), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2023-40743? 4 open source packages ship an affected version, including org.apache.axis:axis and axis:axis. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.axis:axis` | Maven | All versions to 1.4 | None | | `org.apache.axis:axis` | Maven | All versions to 1.4 | None | | `axis:axis` | Maven | All versions to 1.4 | None | | `axis:axis` | Maven | All versions to 1.4 | None | Products: Apache Axis. ## How do I fix CVE-2023-40743? Product is end of life, replace it. ## Is CVE-2023-40743 being exploited? There is no known exploitation of CVE-2023-40743 in the wild and no public exploit code. ## Other vulnerabilities in Apache Axis - [CVE-2019-0227](https://insights.sbomify.com/CVE-2019-0227/): Server Side Request Forgery in Apache Axis (high 7.5) - [CVE-2023-51441](https://insights.sbomify.com/CVE-2023-51441/): Apache Axis 1.x (EOL) may allow SSRF when untrusted input is passed to the service admin HTTP API (high 7.2) - [CVE-2018-8032](https://insights.sbomify.com/CVE-2018-8032/): Moderate severity vulnerability that affects apache axis (medium 6.1) - [CVE-2014-3596](https://insights.sbomify.com/CVE-2014-3596/): Improper Validation of Certificates in apache axis (medium 5.8) - [CVE-2007-2353](https://insights.sbomify.com/CVE-2007-2353/): Apache Axis allows Exposure of Sensitive Information to an Unauthorized Actor (medium 5.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-40743 and fix it if it is affected. What it is: CVE-2023-40743 is a critical server-side request forgery vulnerability in Apache Axis, published on 5 Sep 2023. 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-2023-40743 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.axis:axis (Maven): affected all versions up to 1.4; no fix listed - org.apache.axis:axis (Maven): affected all versions up to 1.4; no fix listed - axis:axis (Maven): affected all versions up to 1.4; no fix listed - axis:axis (Maven): affected all versions up to 1.4; no fix listed 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-2023-40743/ (Markdown: https://insights.sbomify.com/CVE-2023-40743/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-40743 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-40743 - OSV: https://osv.dev/vulnerability/CVE-2023-40743 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-40743/ Summaries are generated and may contain mistakes; the official description above is the record.