{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-22336 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22336 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22336 is a high-severity denial of service vulnerability in IBM Sterling Secure Proxy, published on 23 Feb 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-22336 and fix it if it is affected.\n\nWhat it is: CVE-2022-22336 is a high-severity denial of service vulnerability in IBM Sterling Secure Proxy, published on 23 Feb 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-22336 in the wild and no public exploit code.\n\nAffected product: IBM Sterling Secure Proxy. 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-22336/ (Markdown: https://insights.sbomify.com/CVE-2022-22336/index.md)","id":"CVE-2022-22336","markdown":"https://insights.sbomify.com/CVE-2022-22336/index.md","name":"CVE-2022-22336","record":{"aliases":["GHSA-4qgq-37m7-cp67"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Sterling Secure Proxy","requires_auth":"none","summary":"A remote attacker can cause a denial of service in IBM Sterling Secure Proxy by triggering a resource leak.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"sterling_external_authentication_server","vendor":"ibm"},{"product":"sterling_secure_proxy","vendor":"ibm"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/A:H/S:U/C:N/I:N/AC:L/PR:N/UI:N/RC:C/E:U/RL:O","version":"3.0"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"IBM Sterling External Authentication Server and IBM Sterling Secure Proxy 6.0.3.0, 6.0.2.0, and 3.4.3.2 could allow a remote user to consume resources causing a denial of service due to a resource leak. IBM X-Force ID: 219395.","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":"Denial of service in Sterling Secure Proxy","id":"CVE-2022-22336","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"IBM Sterling B2B Integrator Standard Edition information disclosure","id":"CVE-2022-22337"},"packages":[],"prev":{"headline":"Missing authorization in Robotic Process Automation","id":"CVE-2022-22334"},"products":["Sterling Secure Proxy"],"published":"2022-02-23","related":[{"cvss_score":8.2,"headline":"XML external entity in External Authentication Server","id":"CVE-2020-4462","kev_date_added":null,"published":"2020-07-16"},{"cvss_score":7.8,"headline":"Command injection in Sterling External Authentication Server","id":"CVE-2013-0517","kev_date_added":null,"published":"2020-02-11"},{"cvss_score":6.5,"headline":"Memory corruption in Sterling Secure Proxy","id":"CVE-2022-22333","kev_date_added":null,"published":"2022-02-23"},{"cvss_score":5.9,"headline":"Weak cryptography in Sterling Secure Proxy","id":"CVE-2021-29722","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":5.9,"headline":"Weak cryptography in Sterling Secure Proxy","id":"CVE-2021-29723","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":5.1,"headline":"IBM Sterling Secure Proxy information disclosure","id":"CVE-2023-29261","kev_date_added":null,"published":"2023-09-05"}],"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-17","vendors":["IBM"]},"summary":"A remote attacker can cause a denial of service in IBM Sterling Secure Proxy by triggering a resource leak.","url":"https://insights.sbomify.com/CVE-2022-22336/"}