{"answers":{"affected":"4 open source packages ship an affected version, including org.springframework.security:spring-security-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-0097 in the wild and no public exploit code.","fix":"Upgrade org.springframework.security:spring-security-core to a fixed version for your release line: 3.1.5.RELEASE or 3.2.2.RELEASE.","what":"CVE-2014-0097 is a high-severity authentication bypass vulnerability in Pivotal Spring Security, published on 25 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2014-0097 and fix it if it is affected.\n\nWhat it is: CVE-2014-0097 is a high-severity authentication bypass vulnerability in Pivotal Spring Security, published on 25 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2014-0097 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springframework.security:spring-security-core (Maven): affected from 3.1.0; fixed in 3.1.5.RELEASE\n- org.springframework.security:spring-security-core (Maven): affected from 3.1.0; fixed in 3.1.5.RELEASE\n- org.springframework.security:spring-security-core (Maven): affected from 3.2.0; fixed in 3.2.2.RELEASE\n- org.springframework.security:spring-security-core (Maven): affected from 3.2.0; fixed in 3.2.2.RELEASE\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2014-0097/ (Markdown: https://insights.sbomify.com/CVE-2014-0097/index.md)","id":"CVE-2014-0097","markdown":"https://insights.sbomify.com/CVE-2014-0097/index.md","name":"CVE-2014-0097","record":{"aliases":["GHSA-gv9v-c375-hvmg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Spring Security library","requires_auth":"none","summary":"Attackers can bypass authentication with empty passwords if the LDAP directory allows anonymous binds, affecting Spring Security users.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"spring_security","vendor":"vmware"}],"cvss":{"score":7.3,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"The ActiveDirectoryLdapAuthenticator in Spring Security 3.2.0 to 3.2.1 and 3.1.0 to 3.1.5 does not check the password length. If the directory allows anonymous binds then it may incorrectly authenticate a user who supplies an empty password.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Authentication in Spring Security","id":"CVE-2014-0097","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2014"},"n_packages":4,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2014-0098"},"packages":[{"ecosystem":"Maven","fixed":["3.1.5.RELEASE"],"introduced":["3.1.0"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":null,"source":"GHSA-gv9v-c375-hvmg"},{"ecosystem":"Maven","fixed":["3.1.5.RELEASE"],"introduced":["3.1.0"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":"pkg:maven/org.springframework.security/spring-security-core","source":"GHSA-gv9v-c375-hvmg"},{"ecosystem":"Maven","fixed":["3.2.2.RELEASE"],"introduced":["3.2.0"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":null,"source":"GHSA-gv9v-c375-hvmg"},{"ecosystem":"Maven","fixed":["3.2.2.RELEASE"],"introduced":["3.2.0"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":"pkg:maven/org.springframework.security/spring-security-core","source":"GHSA-gv9v-c375-hvmg"}],"prev":{"headline":"Improper Input Validation in Apache Tomcat","id":"CVE-2014-0096"},"products":["Spring Security"],"published":"2017-05-25","related":[{"cvss_score":9.8,"headline":"Authorization Bypass in Spring Security","id":"CVE-2014-3527","kev_date_added":null,"published":"2017-05-25"},{"cvss_score":9.6,"headline":"Spring Security OAuth2 Authorization Server: Insufficient validation of Dynamic Client Registration metadata","id":"CVE-2026-59354","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.4,"headline":"Spring Security embedded UnboundID LDAP server exposes well-known administrative bind DN on all network interfaces","id":"CVE-2026-59270","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.1,"headline":"Under Some Conditions Spring Security HTTP Headers Are not Written","id":"CVE-2026-22732","kev_date_added":null,"published":"2026-03-19"},{"cvss_score":9.1,"headline":"Access Control Bypass in Spring Security","id":"CVE-2023-34034","kev_date_added":null,"published":"2023-07-19"},{"cvss_score":8.2,"headline":"Spring Security Authorization Server Default Consent Page is vulnerable to Cross-Site Scripting (XSS)","id":"CVE-2026-47877","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":8.1,"headline":"Deserialization of Untrusted Data in Spring Security","id":"CVE-2017-4995","kev_date_added":null,"published":"2017-11-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["Pivotal"]},"summary":"Attackers can bypass authentication with empty passwords if the LDAP directory allows anonymous binds, affecting Spring Security users.","url":"https://insights.sbomify.com/CVE-2014-0097/"}