{"answers":{"affected":"8 open source packages ship an affected version, including org.springframework:spring-context.","exploited":"There is no known exploitation of CVE-2025-22233 in the wild and no public exploit code.","fix":"Upgrade org.springframework:spring-context to a fixed version for your release line: 6.1.20 or 6.2.7.","what":"CVE-2025-22233 is a low-severity missing authorization vulnerability in Spring Framework, published on 16 May 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-22233 and fix it if it is affected.\n\nWhat it is: CVE-2025-22233 is a low-severity missing authorization vulnerability in Spring Framework, published on 16 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-22233 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springframework:spring-context (Maven): affected all versions up to 5.3.39; no fix listed\n- org.springframework:spring-context (Maven): affected all versions up to 5.3.39; no fix listed\n- org.springframework:spring-context (Maven): affected from 6.0.0 up to 6.0.23; no fix listed\n- org.springframework:spring-context (Maven): affected from 6.0.0 up to 6.0.23; no fix listed\n- org.springframework:spring-context (Maven): affected from 6.1.0; fixed in 6.1.20\n- org.springframework:spring-context (Maven): affected from 6.1.0; fixed in 6.1.20\n- org.springframework:spring-context (Maven): affected from 6.2.0; fixed in 6.2.7\n- org.springframework:spring-context (Maven): affected from 6.2.0; fixed in 6.2.7\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-2025-22233/ (Markdown: https://insights.sbomify.com/CVE-2025-22233/index.md)","id":"CVE-2025-22233","markdown":"https://insights.sbomify.com/CVE-2025-22233/index.md","name":"CVE-2025-22233","record":{"aliases":["CLEANSTART-2026-NT49717","CLEANSTART-2026-UT02343","CLSA-2025-1752537764","CLSA-2026-1793094381","DEBIAN-CVE-2025-22233","ECHO-e634-10ea-902d","GHSA-4wp7-92pw-q264","MINI-5h6j-w98g-3rh7","MINI-7p54-m624-p84p","MINI-chq2-w4p8-rx98","MINI-f6rr-x3mx-62mq","MINI-g5g4-348f-crfp","MINI-vqpx-6h2j-fv4r","MINI-wpvr-ww72-g43x","UBUNTU-CVE-2025-22233"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Java web framework","requires_auth":"low_privilege","summary":"Attackers can bypass disallowedFields checks in Spring Framework DataBinder to modify protected object properties, requiring an upgrade to fixed versions.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"CVE-2024-38820 ensured Locale-independent, lowercase conversion for both the configured disallowedFields patterns and for request parameter names. However, there are still cases where it is possible to bypass the disallowedFields checks.\n\nAffected Spring Products and Versions\n\nSpring Framework:\n  *  6.2.0 - 6.2.6\n\n  *  6.1.0 - 6.1.19\n\n  *  6.0.0 - 6.0.27\n\n  *  5.3.0 - 5.3.42\n  *  Older, unsupported versions are also affected\n\nMitigation\n\nUsers of affected versions should upgrade to the corresponding fixed version.\n\nAffected version(s)Fix Version Availability 6.2.x\n 6.2.7\nOSS6.1.x\n 6.1.20\nOSS6.0.x\n 6.0.28\n Commercial https://enterprise.spring.io/ 5.3.x\n 5.3.43\n Commercial https://enterprise.spring.io/ \nNo further mitigation steps are necessary.\n\nGenerally, we recommend using a dedicated model object with properties only for data binding, or using constructor binding since constructor arguments explicitly declare what to bind together with turning off setter binding through the declarativeBinding flag. See the Model Design section in the reference documentation.\n\nFor setting binding, prefer the use of allowedFields (an explicit list) over disallowedFields.\n\nCredit\n\nThis issue was responsibly reported by the TERASOLUNA Framework Development Team from NTT DATA Group Corporation.","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 Framework DataBinder Case Sensitive Match Exception","id":"CVE-2025-22233","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":8,"n_references":1,"next":{"headline":"Spring Security - BCrypt Password Encoder maximum password length breaks timing attack mitigation","id":"CVE-2025-22234"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["5.3.39"],"package":"org.springframework:spring-context","purl":null,"source":"GHSA-4wp7-92pw-q264"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["5.3.39"],"package":"org.springframework:spring-context","purl":"pkg:maven/org.springframework/spring-context","source":"GHSA-4wp7-92pw-q264"},{"ecosystem":"Maven","fixed":[],"introduced":["6.0.0"],"last_affected":["6.0.23"],"package":"org.springframework:spring-context","purl":null,"source":"GHSA-4wp7-92pw-q264"},{"ecosystem":"Maven","fixed":[],"introduced":["6.0.0"],"last_affected":["6.0.23"],"package":"org.springframework:spring-context","purl":"pkg:maven/org.springframework/spring-context","source":"GHSA-4wp7-92pw-q264"},{"ecosystem":"Maven","fixed":["6.1.20"],"introduced":["6.1.0"],"last_affected":[],"package":"org.springframework:spring-context","purl":null,"source":"GHSA-4wp7-92pw-q264"},{"ecosystem":"Maven","fixed":["6.1.20"],"introduced":["6.1.0"],"last_affected":[],"package":"org.springframework:spring-context","purl":"pkg:maven/org.springframework/spring-context","source":"GHSA-4wp7-92pw-q264"},{"ecosystem":"Maven","fixed":["6.2.7"],"introduced":["6.2.0"],"last_affected":[],"package":"org.springframework:spring-context","purl":null,"source":"GHSA-4wp7-92pw-q264"},{"ecosystem":"Maven","fixed":["6.2.7"],"introduced":["6.2.0"],"last_affected":[],"package":"org.springframework:spring-context","purl":"pkg:maven/org.springframework/spring-context","source":"GHSA-4wp7-92pw-q264"}],"prev":{"headline":"Spring Cloud Config Server May Not Use Vault Token Sent By Clients","id":"CVE-2025-22232"},"products":["Spring Framework"],"published":"2025-05-16","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-17","vendors":["Spring"]},"summary":"Attackers can bypass disallowedFields checks in Spring Framework DataBinder to modify protected object properties, requiring an upgrade to fixed versions.","url":"https://insights.sbomify.com/CVE-2025-22233/"}