{"answers":{"affected":"2 open source packages ship an affected version, including org.springframework.session:spring-session-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-20866 in the wild and no public exploit code.","fix":"Upgrade org.springframework.session:spring-session-core to 3.0.1 or later.","what":"CVE-2023-20866 is a medium-severity vulnerability in Spring Session, published on 13 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-20866 and fix it if it is affected.\n\nWhat it is: CVE-2023-20866 is a medium-severity vulnerability in Spring Session, published on 13 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-20866 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springframework.session:spring-session-core (Maven): affected from 3.0.0; fixed in 3.0.1\n- org.springframework.session:spring-session-core (Maven): affected from 3.0.0; fixed in 3.0.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-2023-20866/ (Markdown: https://insights.sbomify.com/CVE-2023-20866/index.md)","id":"CVE-2023-20866","markdown":"https://insights.sbomify.com/CVE-2023-20866/index.md","name":"CVE-2023-20866","record":{"aliases":["GHSA-r7qr-f43m-pxfr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Java session library","requires_auth":"low_privilege","summary":"Attackers with log access can steal session IDs from standard output when using HeaderHttpSessionIdResolver, enabling session hijacking.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"spring_session","vendor":"vmware"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In Spring Session version 3.0.0, the session id can be logged to the standard output stream. This vulnerability exposes sensitive information to those who have access to the application logs and can be used for session hijacking. Specifically, an application is vulnerable if it is using HeaderHttpSessionIdResolver.","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 Session session ID can be logged to the standard output stream","id":"CVE-2023-20866","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":1,"next":{"headline":"VMware Tools Authentication Bypass","id":"CVE-2023-20867"},"packages":[{"ecosystem":"Maven","fixed":["3.0.1"],"introduced":["3.0.0"],"last_affected":[],"package":"org.springframework.session:spring-session-core","purl":null,"source":"GHSA-r7qr-f43m-pxfr"},{"ecosystem":"Maven","fixed":["3.0.1"],"introduced":["3.0.0"],"last_affected":[],"package":"org.springframework.session:spring-session-core","purl":"pkg:maven/org.springframework.session/spring-session-core","source":"GHSA-r7qr-f43m-pxfr"}],"prev":{"headline":"Command injection in VMware Aria Operations for Logs (formerly vRealize Log Insight)","id":"CVE-2023-20865"},"products":["Spring Session"],"published":"2023-04-13","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":"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-07","vendors":["n/a"]},"summary":"Attackers with log access can steal session IDs from standard output when using HeaderHttpSessionIdResolver, enabling session hijacking.","url":"https://insights.sbomify.com/CVE-2023-20866/"}