{"answers":{"affected":"4 open source packages ship an affected version, including org.springframework.security:spring-security-core and org.springframework:spring-core. It affects 3 products.","exploited":"There is no known exploitation of CVE-2016-5007 in the wild and no public exploit code.","fix":"Upgrade org.springframework.security:spring-security-core to 4.1.1 or later.","what":"CVE-2016-5007 is a high-severity missing authorization vulnerability in Vmware Spring Framework, 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-2016-5007 and fix it if it is affected.\n\nWhat it is: CVE-2016-5007 is a high-severity missing authorization vulnerability in Vmware Spring Framework, 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-2016-5007 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springframework.security:spring-security-core (Maven): affected all versions; fixed in 4.1.1\n- org.springframework.security:spring-security-core (Maven): affected all versions; fixed in 4.1.1\n- org.springframework:spring-core (Maven): affected all versions; fixed in 4.3.1\n- org.springframework:spring-core (Maven): affected all versions; fixed in 4.3.1\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-2016-5007/ (Markdown: https://insights.sbomify.com/CVE-2016-5007/index.md)","id":"CVE-2016-5007","markdown":"https://insights.sbomify.com/CVE-2016-5007/index.md","name":"CVE-2016-5007","record":{"aliases":["CLSA-2026-1778028246","DEBIAN-CVE-2016-5007","GHSA-8crv-49fr-2h6j","OESA-2021-1416","ROOT-APP-MAVEN-CVE-2016-5007","UBUNTU-CVE-2016-5007"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Spring Security library","requires_auth":"none","summary":"Attackers can bypass Spring Security authorization checks by exploiting URL pattern matching discrepancies between Spring Security and Spring Framework.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"spring_framework","vendor":"pivotal_software"},{"product":"spring_framework","vendor":"vmware"},{"product":"spring_security","vendor":"vmware"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Both Spring Security 3.2.x, 4.0.x, 4.1.0 and the Spring Framework 3.2.x, 4.0.x, 4.1.x, 4.2.x rely on URL pattern mappings for authorization and for mapping requests to controllers respectively. Differences in the strictness of the pattern matching mechanisms, for example with regards to space trimming in path segments, can lead Spring Security to not recognize certain paths as not protected that are in fact mapped to Spring MVC controllers that should be protected. The problem is compounded by the fact that the Spring Framework provides richer features with regards to pattern matching as well as by the fact that pattern matching in each Spring Security and the Spring Framework can easily be customized creating additional differences.","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":"Spring Security and Spring Framework may not recognize certain paths that should be protected","id":"CVE-2016-5007","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"vmware:spring_framework","products":["vmware:spring_framework"],"type":"missing_authorization","year":"2016"},"n_packages":4,"n_references":4,"next":{"headline":"Auth bypass in n/a","id":"CVE-2016-5008"},"packages":[{"ecosystem":"Maven","fixed":["4.1.1"],"introduced":["0"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":null,"source":"GHSA-8crv-49fr-2h6j"},{"ecosystem":"Maven","fixed":["4.1.1"],"introduced":["0"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":"pkg:maven/org.springframework.security/spring-security-core","source":"GHSA-8crv-49fr-2h6j"},{"ecosystem":"Maven","fixed":["4.3.1"],"introduced":["0"],"last_affected":[],"package":"org.springframework:spring-core","purl":null,"source":"GHSA-8crv-49fr-2h6j"},{"ecosystem":"Maven","fixed":["4.3.1"],"introduced":["0"],"last_affected":[],"package":"org.springframework:spring-core","purl":"pkg:maven/org.springframework/spring-core","source":"GHSA-8crv-49fr-2h6j"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2016-5006"},"products":["Spring Framework","Spring Security"],"published":"2017-05-25","related":[{"cvss_score":8.8,"headline":"Improper Restriction of XML External Entity Reference in Spring Framework","id":"CVE-2014-0225","kev_date_added":null,"published":"2017-05-25"},{"cvss_score":7.5,"headline":"Pivotal Spring Framework Paths provided to the ResourceServlet were not properly sanitized","id":"CVE-2016-9878","kev_date_added":null,"published":"2016-12-29"},{"cvss_score":6.8,"headline":"Cross-Site Request Forgery in Spring Framework","id":"CVE-2013-6429","kev_date_added":null,"published":"2014-01-26"},{"cvss_score":5.4,"headline":"Improper Neutralization of Input During Web Page Generation in Spring Framework","id":"CVE-2013-6430","kev_date_added":null,"published":"2020-01-10"},{"cvss_score":5,"headline":"Moderate severity vulnerability that affects org.springframework:spring-core","id":"CVE-2015-0201","kev_date_added":null,"published":"2015-03-10"},{"cvss_score":5,"headline":"Improper Limitation of a Pathname to a Restricted Directory in Spring Framework","id":"CVE-2014-3578","kev_date_added":null,"published":"2015-02-19"}],"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 Spring Security authorization checks by exploiting URL pattern matching discrepancies between Spring Security and Spring Framework.","url":"https://insights.sbomify.com/CVE-2016-5007/"}