{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-4882 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-4882 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-4882 is a medium-severity server-side request forgery vulnerability in IBM Planning Analytics, published on 22 Mar 2021. 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-2020-4882 and fix it if it is affected.\n\nWhat it is: CVE-2020-4882 is a medium-severity server-side request forgery vulnerability in IBM Planning Analytics, published on 22 Mar 2021. 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-2020-4882 in the wild and no public exploit code.\n\nAffected product: IBM Planning Analytics. 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-4882/ (Markdown: https://insights.sbomify.com/CVE-2020-4882/index.md)","id":"CVE-2020-4882","markdown":"https://insights.sbomify.com/CVE-2020-4882/index.md","name":"CVE-2020-4882","record":{"aliases":["GHSA-fq78-33g3-p22q"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Planning Analytics","requires_auth":"none","summary":"Attackers can exploit SSRF in IBM Planning Analytics to access internal networks or local files via crafted URLs.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"planning_analytics","vendor":"ibm"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.0/S:C/AC:L/A:N/UI:R/AV:N/I:L/PR:N/C:L/E:U/RL:O/RC:C","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"IBM Planning Analytics 2.0 could be vulnerable to a Server-Side Request Forgery (SSRF) attack by constucting URLs from user-controlled data . This could enable attackers to make arbitrary requests to the internal network or to the local file system. IBM X-Force ID: 190852.","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 Planning Analytics","id":"CVE-2020-4882","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in QRadar SIEM","id":"CVE-2020-4883"},"packages":[],"prev":{"headline":"Information disclosure in Planning Analytics","id":"CVE-2020-4881"},"products":["Planning Analytics"],"published":"2021-03-22","related":[{"cvss_score":10,"headline":"IBM Planning Analytics Remote Code Execution","id":"CVE-2019-4716","kev_date_added":"2021-11-03","published":"2019-12-18"},{"cvss_score":8.8,"headline":"IBM Planning Analytics Local is affected by security vulnerabilities","id":"CVE-2026-19620","kev_date_added":null,"published":"2026-10-12"},{"cvss_score":8.8,"headline":"IBM Planning Analytics Local is affected by security vulnerabilities","id":"CVE-2026-19622","kev_date_added":null,"published":"2026-10-12"},{"cvss_score":8.2,"headline":"IBM Planning Analytics Local is affected by security vulnerabilities","id":"CVE-2026-19627","kev_date_added":null,"published":"2026-10-12"},{"cvss_score":8,"headline":"IBM Planning Analytics file upload","id":"CVE-2024-25034","kev_date_added":null,"published":"2025-01-24"},{"cvss_score":8,"headline":"IBM Planning Analytics file upload","id":"CVE-2024-40693","kev_date_added":null,"published":"2025-01-24"},{"cvss_score":8,"headline":"IBM Planning Analytics file upload","id":"CVE-2023-42017","kev_date_added":null,"published":"2023-12-22"}],"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-09-16","vendors":["IBM"]},"summary":"Attackers can exploit SSRF in IBM Planning Analytics to access internal networks or local files via crafted URLs.","url":"https://insights.sbomify.com/CVE-2020-4882/"}