https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 20:27:08 +0000 https://cve.radiocsirt.org/vuln/bdu:2023-07271 bdu:2023-07271 https://cve.radiocsirt.org/vuln/bdu:2023-07271 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0090 certfr-2024-avi-0090 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0090 https://cve.radiocsirt.org/vuln/cnvd-2023-70275 cnvd-2023-70275 https://cve.radiocsirt.org/vuln/cnvd-2023-70275 https://cve.radiocsirt.org/vuln/euvd-2026-216778 EUVD-2026-216778 https://cve.radiocsirt.org/vuln/euvd-2026-216778 https://cve.radiocsirt.org/vuln/fkie_cve-2023-40743 <p>** UNSUPPORTED WHEN ASSIGNED ** When integrating Apache Axis 1.x in an application, it may not have been obvious that looking up a service through &#34;ServiceFactory.getService&#34; 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.</p> <p>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 &#34;ServiceFactory.getService&#34;, 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.</p> <p>** UNSUPPORTED WHEN ASSIGNED ** When integrating Apache Axis 1.x in an application, it may not have been obvious that looking up a service through &#34;ServiceFactory.getService&#34; 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.</p> <p>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 &#34;ServiceFactory.getService&#34;, 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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-40743 https://cve.radiocsirt.org/vuln/ghsa-rmqp-9w4c-gc7w <p><strong>Affected:</strong> Maven: org.apache.axis:axis, Maven: axis:axis</p> <p>When integrating Apache Axis 1.x in an application, it may not have been obvious that looking up a service through &#34;ServiceFactory.getService&#34; 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.</p> <p>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 &#34;ServiceFactory.getService&#34;, 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.</p> <p><strong>Affected:</strong> Maven: org.apache.axis:axis, Maven: axis:axis</p> <p>When integrating Apache Axis 1.x in an application, it may not have been obvious that looking up a service through &#34;ServiceFactory.getService&#34; 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.</p> <p>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 &#34;ServiceFactory.getService&#34;, 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.</p> https://cve.radiocsirt.org/vuln/ghsa-rmqp-9w4c-gc7w https://cve.radiocsirt.org/vuln/gsd-2023-40743 gsd-2023-40743 https://cve.radiocsirt.org/vuln/gsd-2023-40743 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-40743 <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: axis, Ubuntu:Pro:18.04:LTS: axis, Ubuntu:20.04:LTS: axis, Ubuntu:22.04:LTS: axis</p> <p>** UNSUPPORTED WHEN ASSIGNED ** When integrating Apache Axis 1.x in an application, it may not have been obvious that looking up a service through &#34;ServiceFactory.getService&#34; 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 &#34;ServiceFactory.getService&#34;, 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.</p> <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: axis, Ubuntu:Pro:18.04:LTS: axis, Ubuntu:20.04:LTS: axis, Ubuntu:22.04:LTS: axis</p> <p>** UNSUPPORTED WHEN ASSIGNED ** When integrating Apache Axis 1.x in an application, it may not have been obvious that looking up a service through &#34;ServiceFactory.getService&#34; 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 &#34;ServiceFactory.getService&#34;, 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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-40743 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0543 <p>Ein entfernter Angreifer kann mehrere Schwachstellen in IBM WebSphere Service Registry and Repository ausnutzen, um beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu verursachen oder vertrauliche Informationen offenzulegen.</p> <p>Ein entfernter Angreifer kann mehrere Schwachstellen in IBM WebSphere Service Registry and Repository ausnutzen, um beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu verursachen oder vertrauliche Informationen offenzulegen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0543