{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-22332 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22332 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22332 is a medium-severity vulnerability in IBM Sterling Partner Engagement Manager, published on 1 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-22332 and fix it if it is affected.\n\nWhat it is: CVE-2022-22332 is a medium-severity vulnerability in IBM Sterling Partner Engagement Manager, published on 1 Apr 2022. 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-2022-22332 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-22332/ (Markdown: https://insights.sbomify.com/CVE-2022-22332/index.md)","id":"CVE-2022-22332","markdown":"https://insights.sbomify.com/CVE-2022-22332/index.md","name":"CVE-2022-22332","record":{"aliases":["GHSA-g96j-fpm6-qgvc"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Sterling Partner Engagement Manager","requires_auth":"none","summary":"Attackers can impersonate users due to missing JWT revocation, requiring IBM Sterling Partner Engagement Manager users to apply security patches.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"partner_engagement_manager","vendor":"ibm"}],"cvss":{"score":5.6,"severity":"medium","source":"cna","vector":"CVSS:3.0/PR:N/AC:H/UI:N/AV:N/S:U/A:L/C:L/I:L/E:U/RL:O/RC:C","version":"3.0"},"cwes":[{"id":"CWE-672","name":"Operation on a Resource after Expiration or Release"}],"description":"IBM Sterling Partner Engagement Manager 6.2.0 could allow an attacker to impersonate another user due to missing revocation mechanism for the JWT token. IBM X-Force ID: 219131.","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":"Security feature bypass in Sterling Partner Engagement Manager","id":"CVE-2022-22332","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Sterling Secure Proxy","id":"CVE-2022-22333"},"packages":[],"prev":{"headline":"Missing authorization in SterlingPartner Engagement Manager","id":"CVE-2022-22331"},"products":["Sterling Partner Engagement Manager"],"published":"2022-04-01","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.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 impersonate users due to missing JWT revocation, requiring IBM Sterling Partner Engagement Manager users to apply security patches.","url":"https://insights.sbomify.com/CVE-2022-22332/"}