{"id":"CVE-2017-8028","aliases":["DEBIAN-CVE-2017-8028","DLA-1180-1","DSA-4046-1","EUVD-2022-4787","GHSA-pjqh-2jcc-5j84","MGASA-2018-0235","UBUNTU-CVE-2017-8028"],"status":"published","title":"Improper Authentication in Pivotal Spring-LDAP","description":"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.","severity":{"version":"3.0","score":8.1,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-07","score":0.02606,"percentile":0.85475,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-287"],"published":"2017-11-19T00:00:00Z","modified":"2026-06-17T01:25:39Z","fixes":[{"ecosystem":"Maven","package":"org.springframework.ldap:spring-ldap-core","fixed_in":["2.3.2"],"sources":["ghsa","osv"]},{"ecosystem":"Debian:7","package":"libspring-ldap-java","fixed_in":["1.3.1.RELEASE-4+deb7u1"],"sources":["osv"]},{"ecosystem":"Debian:8","package":"libspring-ldap-java","fixed_in":["1.3.1.RELEASE-5+deb8u1"],"sources":["osv"]},{"ecosystem":"Mageia:6","package":"spring-ldap","fixed_in":["1.3.1-14.1.mga6"],"sources":["osv"]},{"ecosystem":"Ubuntu:14.04:LTS","package":"libspring-ldap-java","fixed_in":["1.3.1.RELEASE-4+deb7u1build0.14.04.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"org.springframework.ldap:spring-ldap-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.3.0"},{"last_affected":"2.3.1"},{"fixed":"2.3.2"}]}]},{"source":"osv","ecosystem":"Debian:7","package":"libspring-ldap-java","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.1.RELEASE-4+deb7u1"}]}],"versions":["1.3.1.RELEASE-4"]},{"source":"osv","ecosystem":"Debian:8","package":"libspring-ldap-java","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.1.RELEASE-5+deb8u1"}]}],"versions":["1.3.1.RELEASE-5"]},{"source":"osv","ecosystem":"Maven","package":"org.springframework.ldap:spring-ldap-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.3.0"},{"fixed":"2.3.2"}]}],"versions":["1.3.0.RELEASE","1.3.1.RELEASE","1.3.2.RELEASE","2.0.0.RELEASE","2.0.1.RELEASE","2.0.2.RELEASE","2.0.3.RELEASE","2.0.4.RELEASE","2.1.0.RELEASE","2.2.0.RELEASE","2.2.1.RELEASE","2.3.0.RELEASE","2.3.1.RELEASE"]},{"source":"osv","ecosystem":"Mageia:6","package":"spring-ldap","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.1-14.1.mga6"}]}]},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"libspring-ldap-java","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.1.RELEASE-4+deb7u1build0.14.04.1"}]}],"versions":["1.3.1.RELEASE-4"]}],"products":[{"vendor":"debian","product":"debian_linux"},{"vendor":"pivotal_software","product":"spring-ldap"}],"references":[{"url":"https://access.redhat.com/errata/RHSA-2018:0319","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","web"]},{"url":"https://www.debian.org/security/2017/dsa-4046","tags":["vendor-advisory","x_refsource_DEBIAN","x_transferred","Issue Tracking","Third Party Advisory","web"]},{"url":"https://lists.debian.org/debian-lts-announce/2017/11/msg00026.html","tags":["mailing-list","x_refsource_MLIST","x_transferred","web"]},{"url":"https://www.oracle.com/security-alerts/cpujan2021.html","tags":["x_refsource_MISC","x_transferred","web"]},{"url":"https://pivotal.io/security/cve-2017-8028","tags":["x_refsource_CONFIRM","x_transferred","Issue Tracking","Vendor Advisory","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-8028","tags":["advisory"]},{"url":"https://github.com/spring-projects/spring-ldap/commit/08e8ae289bbd1b581986c7238604a147119c1336","tags":["web"]},{"url":"https://github.com/advisories/GHSA-pjqh-2jcc-5j84"},{"url":"https://github.com/spring-projects/spring-ldap","tags":["package"]},{"url":"https://advisories.mageia.org/MGASA-2018-0235.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=22085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-8028","tags":["report"]},{"url":"https://github.com/spring-projects/spring-ldap/issues/430","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-8028","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2017-8028","description":"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.","status":"published","published":"2017-11-27T10:00:00Z","modified":"2024-08-05T16:19:29.484Z","updated_at":"2026-11-02T14:33:14.89365Z"}],"euvd":[{"id":"EUVD-2022-4787","description":"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.","status":"published","published":"2017-11-27T10:00:00Z","modified":"2024-08-05T16:19:29Z","updated_at":"2026-11-03T02:39:05.933017Z"}],"ghsa":[{"id":"GHSA-pjqh-2jcc-5j84","title":"Improper Authentication in Pivotal Spring-LDAP","description":"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.","status":"published","published":"2022-05-13T01:12:09Z","modified":"2024-04-05T18:51:09Z","cvss":[{"version":"3.0","score":8.1,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-287"],"updated_at":"2026-11-02T14:37:42.744468Z"}],"nvd":[{"id":"CVE-2017-8028","description":"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.","status":"published","published":"2017-11-27T10:29:00.72Z","modified":"2026-06-17T01:25:39.727Z","cvss":[{"version":"3.0","score":8.1,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":5.1,"vector":"AV:N/AC:H/Au:N/C:P/I:P/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-287"],"updated_at":"2026-11-02T14:04:09.7374Z"}],"osv":[{"id":"GHSA-pjqh-2jcc-5j84","title":"Improper Authentication in Pivotal Spring-LDAP","description":"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.","status":"published","published":"2022-05-13T01:12:09Z","modified":"2024-04-10T18:57:08.806686Z","cvss":[{"version":"3.0","score":8.1,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-287"],"updated_at":"2026-11-02T15:46:53.244788Z"},{"id":"UBUNTU-CVE-2017-8028","description":"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.","status":"published","published":"2017-11-27T10:29:00Z","modified":"2025-09-08T16:44:14Z","cvss":[{"version":"3.0","score":8.1,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:54:15.773974Z"},{"id":"DLA-1180-1","title":"libspring-ldap-java - security update","status":"published","published":"2017-11-19T00:00:00Z","modified":"2026-03-09T01:01:44.004851Z","updated_at":"2026-11-02T15:46:09.336894Z"},{"id":"DSA-4046-1","title":"libspring-ldap-java - security update","status":"published","published":"2017-11-22T00:00:00Z","modified":"2026-03-09T01:21:30.462308Z","updated_at":"2026-11-02T15:46:16.523846Z"},{"id":"MGASA-2018-0235","title":"Updated spring-ldap packages fix security vulnerability","description":"It was discovered that spring-ldap would under some circumstances allow\nauthentication with a correct username but an arbitrary password\n(CVE-2017-8028).\n","status":"published","published":"2018-05-16T08:24:56Z","modified":"2026-04-16T06:24:20.599950252Z","updated_at":"2026-11-02T15:49:40.442238Z"}]}}