{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-22359 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22359 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22359 is a medium-severity vulnerability in IBM Sterling Partner Engagement Manager, published on 19 Jul 2022. 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-2022-22359 and fix it if it is affected.\n\nWhat it is: CVE-2022-22359 is a medium-severity vulnerability in IBM Sterling Partner Engagement Manager, published on 19 Jul 2022. 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-2022-22359 in the wild and no public exploit code.\n\nAffected product: IBM Sterling Partner Engagement Manager. 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-2022-22359/ (Markdown: https://insights.sbomify.com/CVE-2022-22359/index.md)","id":"CVE-2022-22359","markdown":"https://insights.sbomify.com/CVE-2022-22359/index.md","name":"CVE-2022-22359","record":{"aliases":["GHSA-mq7q-47xg-285x"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Sterling Partner Engagement Manager","requires_auth":"none","summary":"Attackers can trick authenticated users into performing unauthorized actions in IBM Sterling Partner Engagement Manager via cross-site request forgery.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"partner_engagement_manager","vendor":"ibm"},{"product":"partner_engagement_manager_on_cloud\\/saas","vendor":"ibm"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/I:L/AC:L/A:N/S:U/C:N/UI:R/PR:N/AV:N/E:U/RC:C/RL:O","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"IBM Sterling Partner Engagement Manager 6.1.2, 6.2, and Cloud/SasS 22.2 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 220652.","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":"Cross-site request forgery in Sterling Partner Engagement Manager","id":"CVE-2022-22359","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Other in Sterling Partner Engagement Manager","id":"CVE-2022-22360"},"packages":[],"prev":{"headline":"XML external entity in Sterling Partner Engagement Manager","id":"CVE-2022-22358"},"products":["Sterling Partner Engagement Manager","Sterling Partner Engagement Manager on Cloud"],"published":"2022-07-19","related":[{"cvss_score":9.8,"headline":"Deserialization in Partner Engagement Manager","id":"CVE-2021-29781","kev_date_added":null,"published":"2021-07-30"},{"cvss_score":7.5,"headline":"Other in Sterling Partner Engagement Manager","id":"CVE-2022-22360","kev_date_added":null,"published":"2022-07-19"},{"cvss_score":7.1,"headline":"XML external entity in Sterling Partner Engagement Manager","id":"CVE-2022-22358","kev_date_added":null,"published":"2022-07-19"},{"cvss_score":6.2,"headline":"Privilege escalation in SterlingPartner Engagement Manager","id":"CVE-2022-22328","kev_date_added":null,"published":"2022-04-01"},{"cvss_score":5.6,"headline":"Security feature bypass in Sterling Partner Engagement Manager","id":"CVE-2022-22332","kev_date_added":null,"published":"2022-04-01"},{"cvss_score":5.4,"headline":"Server-side request forgery in Sterling Partner Engagement Manager","id":"CVE-2022-22416","kev_date_added":null,"published":"2022-07-19"},{"cvss_score":5.4,"headline":"Cross-site scripting in Sterling Partner Engagement Manager","id":"CVE-2022-22417","kev_date_added":null,"published":"2022-07-19"}],"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 trick authenticated users into performing unauthorized actions in IBM Sterling Partner Engagement Manager via cross-site request forgery.","url":"https://insights.sbomify.com/CVE-2022-22359/"}