{"answers":{"affected":"4 open source packages ship an affected version, including org.springframework.security:spring-security-core and org.springframework.security:spring-security-oauth2-jose. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-15801 in the wild and no public exploit code.","fix":"Upgrade org.springframework.security:spring-security-core to 5.1.2 or later.","what":"CVE-2018-15801 is a low-severity authentication bypass vulnerability in Vmware Spring Framework, published on 19 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-15801 and fix it if it is affected.\n\nWhat it is: CVE-2018-15801 is a low-severity authentication bypass vulnerability in Vmware Spring Framework, published on 19 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-15801 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springframework.security:spring-security-core (Maven): affected from 5.1.0; fixed in 5.1.2\n- org.springframework.security:spring-security-core (Maven): affected from 5.1.0; fixed in 5.1.2\n- org.springframework.security:spring-security-oauth2-jose (Maven): affected from 5.1.0; fixed in 5.1.2\n- org.springframework.security:spring-security-oauth2-jose (Maven): affected from 5.1.0; fixed in 5.1.2\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-2018-15801/ (Markdown: https://insights.sbomify.com/CVE-2018-15801/index.md)","id":"CVE-2018-15801","markdown":"https://insights.sbomify.com/CVE-2018-15801/index.md","name":"CVE-2018-15801","record":{"aliases":["GHSA-27xw-p8v6-9jjr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Spring Security library","requires_auth":"high_privilege","summary":"Attackers can bypass authorization checks in Spring Security if a shared private key is used, allowing forged JWTs to be accepted as valid.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"spring_framework","vendor":"vmware"}],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Spring Security versions 5.1.x prior to 5.1.2 contain an authorization bypass vulnerability during JWT issuer validation. In order to be impacted, the same private key for an honest issuer and a malicious user must be used when signing JWTs. In that case, a malicious user could fashion signed JWTs with the malicious issuer URL that may be granted for the honest issuer.","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":"Authorization Bypass During JWT Issuer Validation with spring-security","id":"CVE-2018-15801","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"vmware:spring_framework","products":["vmware:spring_framework"],"type":"auth_bypass","year":"2018"},"n_packages":4,"n_references":1,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2018-15802"},"packages":[{"ecosystem":"Maven","fixed":["5.1.2"],"introduced":["5.1.0"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":null,"source":"GHSA-27xw-p8v6-9jjr"},{"ecosystem":"Maven","fixed":["5.1.2"],"introduced":["5.1.0"],"last_affected":[],"package":"org.springframework.security:spring-security-core","purl":"pkg:maven/org.springframework.security/spring-security-core","source":"GHSA-27xw-p8v6-9jjr"},{"ecosystem":"Maven","fixed":["5.1.2"],"introduced":["5.1.0"],"last_affected":[],"package":"org.springframework.security:spring-security-oauth2-jose","purl":null,"source":"GHSA-27xw-p8v6-9jjr"},{"ecosystem":"Maven","fixed":["5.1.2"],"introduced":["5.1.0"],"last_affected":[],"package":"org.springframework.security:spring-security-oauth2-jose","purl":"pkg:maven/org.springframework.security/spring-security-oauth2-jose","source":"GHSA-27xw-p8v6-9jjr"}],"prev":{"headline":"Timing attack allows extraction of signing key in Bits Service","id":"CVE-2018-15800"},"products":["Spring Security"],"published":"2018-12-19","related":[{"cvss_score":9.8,"headline":"Spring Framework Improper Path Limitation in XsltView","id":"CVE-2026-47884","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.8,"headline":"Spring Framework Server Sent Event stream corruption while rendering fragments","id":"CVE-2026-47890","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.8,"headline":"Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder","id":"CVE-2026-47891","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.8,"headline":"Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints","id":"CVE-2026-47892","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.8,"headline":"Server Sent Event stream corruption in Spring MVC functional web framework","id":"CVE-2026-59313","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.8,"headline":"Pivotal Spring Framework contains unsafe Java deserialization methods","id":"CVE-2016-1000027","kev_date_added":null,"published":"2020-01-02"},{"cvss_score":9.1,"headline":"Spring Framework Safety Guard Bypass via SpEL Expression Compilation","id":"CVE-2026-59283","kev_date_added":null,"published":"2026-08-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-09-16","vendors":["Spring by Pivotal"]},"summary":"Attackers can bypass authorization checks in Spring Security if a shared private key is used, allowing forged JWTs to be accepted as valid.","url":"https://insights.sbomify.com/CVE-2018-15801/"}