{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-20341 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-20341 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-20341 is a high-severity server-side request forgery vulnerability in n/a, published on 1 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-20341 and fix it if it is affected.\n\nWhat it is: CVE-2020-20341 is a high-severity server-side request forgery vulnerability in n/a, published on 1 Sep 2021. 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-2020-20341 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2020-20341/ (Markdown: https://insights.sbomify.com/CVE-2020-20341/index.md)","id":"CVE-2020-20341","markdown":"https://insights.sbomify.com/CVE-2020-20341/index.md","name":"CVE-2020-20341","record":{"aliases":["GHSA-4pmf-qqvh-jvqv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"YzmCMS","requires_auth":"none","summary":"An attacker can exploit a server-side request forgery vulnerability in YzmCMS to interact with internal systems or external resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yzmcms","vendor":"yzmcms"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"YzmCMS v5.5 contains a server-side request forgery (SSRF) in the grab_image() function.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Server-side request forgery in n/a","id":"CVE-2020-20341","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-20343"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2020-20340"},"products":["n/a"],"published":"2021-09-01","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2018-11554","kev_date_added":null,"published":"2018-06-05"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2022-23383","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-23595","kev_date_added":null,"published":"2023-08-11"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2022-23384","kev_date_added":null,"published":"2022-02-15"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2022-23888","kev_date_added":null,"published":"2022-01-28"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-19951","kev_date_added":null,"published":"2021-09-23"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-20015","kev_date_added":null,"published":"2018-12-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-04","vendors":["n/a"]},"summary":"An attacker can exploit a server-side request forgery vulnerability in YzmCMS to interact with internal systems or external resources.","url":"https://insights.sbomify.com/CVE-2020-20341/"}