https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 09:27:56 +0000 https://cve.radiocsirt.org/vuln/bdu:2021-01068 bdu:2021-01068 https://cve.radiocsirt.org/vuln/bdu:2021-01068 https://cve.radiocsirt.org/vuln/cnvd-2017-35603 cnvd-2017-35603 https://cve.radiocsirt.org/vuln/cnvd-2017-35603 https://cve.radiocsirt.org/vuln/euvd-2026-75087 EUVD-2026-75087 https://cve.radiocsirt.org/vuln/euvd-2026-75087 https://cve.radiocsirt.org/vuln/fkie_cve-2017-8028 <p>In Pivotal Spring-LDAP versions 1.3.0 - 2.3.1, when connected to some LDAP servers, when no additional attributes are bound, and when using LDAP BindAuthenticator with org.springframework.ldap.core.support.DefaultTlsDirContextAuthenticationStrategy as the authentication strategy, and setting userSearch, authentication is allowed with an arbitrary password when the username is correct. This occurs because some LDAP vendors require an explicit operation for the LDAP bind to take effect.</p> <p>In Pivotal Spring-LDAP versions 1.3.0 - 2.3.1, when connected to some LDAP servers, when no additional attributes are bound, and when using LDAP BindAuthenticator with org.springframework.ldap.core.support.DefaultTlsDirContextAuthenticationStrategy as the authentication strategy, and setting userSearch, authentication is allowed with an arbitrary password when the username is correct. This occurs because some LDAP vendors require an explicit operation for the LDAP bind to take effect.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2017-8028 https://cve.radiocsirt.org/vuln/ghsa-pjqh-2jcc-5j84 <p><strong>Affected:</strong> Maven: org.springframework.ldap:spring-ldap-core</p> <p>In Pivotal Spring-LDAP versions 1.3.0 - 2.3.1, when connected to some LDAP servers, when no additional attributes are bound, and when using LDAP BindAuthenticator with org.springframework.ldap.core.support.DefaultTlsDirContextAuthenticationStrategy as the authentication strategy, and setting userSearch, authentication is allowed with an arbitrary password when the username is correct. This occurs because some LDAP vendors require an explicit operation for the LDAP bind to take effect.</p> <p><strong>Affected:</strong> Maven: org.springframework.ldap:spring-ldap-core</p> <p>In Pivotal Spring-LDAP versions 1.3.0 - 2.3.1, when connected to some LDAP servers, when no additional attributes are bound, and when using LDAP BindAuthenticator with org.springframework.ldap.core.support.DefaultTlsDirContextAuthenticationStrategy as the authentication strategy, and setting userSearch, authentication is allowed with an arbitrary password when the username is correct. This occurs because some LDAP vendors require an explicit operation for the LDAP bind to take effect.</p> https://cve.radiocsirt.org/vuln/ghsa-pjqh-2jcc-5j84 https://cve.radiocsirt.org/vuln/gsd-2017-8028 gsd-2017-8028 https://cve.radiocsirt.org/vuln/gsd-2017-8028 https://cve.radiocsirt.org/vuln/rhsa-2018:0319 <p>Hawtio: Unrestricted file upload leads to RCE batik: XML external entity processing vulnerability spring-ldap: Authentication with userSearch and STARTTLS allows authentication with arbitrary password camel-hessian: Apache Camel&#39;s Hessian unmarshalling operation is vulnerable to Remote Code Execution attacks camel-castor: Apache Camel&#39;s Castor unmarshalling operation is vulnerable to Remote Code Execution attacks</p> <p>Hawtio: Unrestricted file upload leads to RCE batik: XML external entity processing vulnerability spring-ldap: Authentication with userSearch and STARTTLS allows authentication with arbitrary password camel-hessian: Apache Camel&#39;s Hessian unmarshalling operation is vulnerable to Remote Code Execution attacks camel-castor: Apache Camel&#39;s Castor unmarshalling operation is vulnerable to Remote Code Execution attacks</p> https://cve.radiocsirt.org/vuln/rhsa-2018:0319 https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-8028 <p><strong>Affected:</strong> Ubuntu:14.04:LTS: libspring-ldap-java</p> <p>In Pivotal Spring-LDAP versions 1.3.0 - 2.3.1, when connected to some LDAP servers, when no additional attributes are bound, and when using LDAP BindAuthenticator with org.springframework.ldap.core.support.DefaultTlsDirContextAuthenticationStrategy as the authentication strategy, and setting userSearch, authentication is allowed with an arbitrary password when the username is correct. This occurs because some LDAP vendors require an explicit operation for the LDAP bind to take effect.</p> <p><strong>Affected:</strong> Ubuntu:14.04:LTS: libspring-ldap-java</p> <p>In Pivotal Spring-LDAP versions 1.3.0 - 2.3.1, when connected to some LDAP servers, when no additional attributes are bound, and when using LDAP BindAuthenticator with org.springframework.ldap.core.support.DefaultTlsDirContextAuthenticationStrategy as the authentication strategy, and setting userSearch, authentication is allowed with an arbitrary password when the username is correct. This occurs because some LDAP vendors require an explicit operation for the LDAP bind to take effect.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-8028