axis: ** UNSUPPORTED WHEN ASSIGNED ** When integrating Apache Axis 1.x in an application, it may not have been obvious that...
CVE-2023-40743 is fixed in 2 products on 1 platform, first by libaxis-java 1.4-25ubuntu0.1~esm1, released September 5, 2023. It is not reported as exploited. Patch Radar priority: Urgent.
** 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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| axis · Debian 12.15 (bookworm) | 1.4-28+deb12u1 | DEBIAN-CVE-2023-40743 | Sep 5, 2023 |
| axis · Debian 13.5 (trixie) | 1.4-29 | DEBIAN-CVE-2023-40743 | Sep 5, 2023 |
| axis · Debian 14 | 1.4-29 | DEBIAN-CVE-2023-40743 | Sep 5, 2023 |
| libaxis-java · Ubuntu 18.04.6 LTS (bionic) | 1.4-25ubuntu0.1~esm1 | libaxis-java 1.4-25ubuntu0.1~esm1 | Sep 5, 2023 |
| libaxis-java · Ubuntu 20.04 LTS (focal) | 1.4-28+deb10u1build0.20.04.1 | libaxis-java 1.4-28+deb10u1build0.20.04.1 | Sep 5, 2023 |
| libaxis-java · Ubuntu 22.04.1 LTS (jammy) | 1.4-28+deb10u1build0.22.04.1 | libaxis-java 1.4-28+deb10u1build0.22.04.1 | Sep 5, 2023 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.