{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34362 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-34362 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-34362 is a medium-severity cross-site scripting vulnerability in IBM Sterling Secure Proxy, published on 8 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-34362 and fix it if it is affected.\n\nWhat it is: CVE-2022-34362 is a medium-severity cross-site scripting vulnerability in IBM Sterling Secure Proxy, published on 8 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-34362 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-34362/ (Markdown: https://insights.sbomify.com/CVE-2022-34362/index.md)","id":"CVE-2022-34362","markdown":"https://insights.sbomify.com/CVE-2022-34362/index.md","name":"CVE-2022-34362","record":{"aliases":["GHSA-h63x-q57p-mpgf"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Secure Proxy","requires_auth":"low_privilege","summary":"Attackers can inject malicious HOST headers to execute cross-site scripting, poison caches, or hijack sessions in IBM Sterling Secure Proxy.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"sterling_secure_proxy","vendor":"ibm"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"IBM Sterling Secure Proxy 6.0.3 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers. This could allow an attacker to conduct various attacks against the vulnerable system, including cross-site scripting, cache poisoning or session hijacking. IBM X-Force ID: 230523.","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":"IBM Sterling Secure Proxy HOST header injection","id":"CVE-2022-34362","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Dell Unisphere for PowerMax vApp version prior to 10.0.0.2, contains an authorization bypass vulnerability in the Unisphere for VMAX applica","id":"CVE-2022-34363"},"packages":[],"prev":{"headline":"IBM Sterling Secure Proxy information disclosure","id":"CVE-2022-34361"},"products":["Sterling Secure Proxy"],"published":"2023-02-08","related":[{"cvss_score":9.1,"headline":"IBM Sterling Secure Proxy improper input validation","id":"CVE-2024-38337","kev_date_added":null,"published":"2025-01-19"},{"cvss_score":9.1,"headline":"IBM Sterling Secure Proxy improper input validation","id":"CVE-2024-41783","kev_date_added":null,"published":"2025-01-19"},{"cvss_score":7.5,"headline":"IBM Sterling Secure Proxy directory traversal","id":"CVE-2024-41784","kev_date_added":null,"published":"2024-11-15"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2016-6023","kev_date_added":null,"published":"2016-10-06"},{"cvss_score":6.1,"headline":"IBM Secure Proxy cross-site scripting","id":"CVE-2023-47162","kev_date_added":null,"published":"2024-03-15"},{"cvss_score":6.1,"headline":"IBM Secure Proxy cross-site scripting","id":"CVE-2023-47699","kev_date_added":null,"published":"2024-03-15"},{"cvss_score":6.1,"headline":"Security feature bypass in n/a","id":"CVE-2016-6027","kev_date_added":null,"published":"2016-10-06"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-24","vendors":["IBM"]},"summary":"Attackers can inject malicious HOST headers to execute cross-site scripting, poison caches, or hijack sessions in IBM Sterling Secure Proxy.","url":"https://insights.sbomify.com/CVE-2022-34362/"}