{"answers":{"affected":"2 open source packages ship an affected version, including org.hswebframework.web:hsweb-commons. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20595 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20595 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20595 is a high-severity vulnerability in n/a, published on 30 Dec 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-20595 and fix it if it is affected.\n\nWhat it is: CVE-2018-20595 is a high-severity vulnerability in n/a, published on 30 Dec 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-20595 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.hswebframework.web:hsweb-commons (Maven): affected all versions up to 3.0.4; no fix listed\n- org.hswebframework.web:hsweb-commons (Maven): affected all versions up to 3.0.4; no fix listed\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-20595/ (Markdown: https://insights.sbomify.com/CVE-2018-20595/index.md)","id":"CVE-2018-20595","markdown":"https://insights.sbomify.com/CVE-2018-20595/index.md","name":"CVE-2018-20595","record":{"aliases":["GHSA-4rm3-4mq4-mfwr"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"hsweb framework","requires_auth":"none","summary":"Attackers can perform CSRF attacks in hsweb by bypassing OAuth2 state validation, potentially leading to account takeover.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hsweb","vendor":"hsweb"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A CSRF issue was discovered in web/authorization/oauth2/controller/OAuth2ClientController.java in hsweb 3.0.4 because the state parameter in the request is not compared with the state parameter in the session after user authentication is successful.","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":false,"headline":"Cross-Site Request Forgery (CSRF) in hswebframework.web:hsweb-commons","id":"CVE-2018-20595","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"Jspxcms v9.0.0 allows SSRF.","id":"CVE-2018-20596"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["3.0.4"],"package":"org.hswebframework.web:hsweb-commons","purl":null,"source":"GHSA-4rm3-4mq4-mfwr"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["3.0.4"],"package":"org.hswebframework.web:hsweb-commons","purl":"pkg:maven/org.hswebframework.web/hsweb-commons","source":"GHSA-4rm3-4mq4-mfwr"}],"prev":{"headline":"Moderate severity vulnerability that affects org.hswebframework.web:hsweb-commons","id":"CVE-2018-20594"},"products":["n/a"],"published":"2018-12-30","related":[{"cvss_score":6.1,"headline":"Moderate severity vulnerability that affects org.hswebframework.web:hsweb-commons","id":"CVE-2018-20594","kev_date_added":null,"published":"2018-12-30"}],"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-05","vendors":["n/a"]},"summary":"Attackers can perform CSRF attacks in hsweb by bypassing OAuth2 state validation, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2018-20595/"}