{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-36775 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36775 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36775 is a medium-severity vulnerability in Ibm Security Verify Access, published on 17 Feb 2023. 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-36775 and fix it if it is affected.\n\nWhat it is: CVE-2022-36775 is a medium-severity vulnerability in Ibm Security Verify Access, published on 17 Feb 2023. 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-36775 in the wild and no public exploit code.\n\nAffected product: Ibm Security Verify Access. 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-36775/ (Markdown: https://insights.sbomify.com/CVE-2022-36775/index.md)","id":"CVE-2022-36775","markdown":"https://insights.sbomify.com/CVE-2022-36775/index.md","name":"CVE-2022-36775","record":{"aliases":["GHSA-5gjp-557x-hq5g"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Security Verify Access","requires_auth":"none","summary":"Attackers can inject HTTP headers to enable XSS, cache poisoning, or session hijacking in IBM Security Verify Access.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_verify_access","vendor":"ibm"},{"product":"security_verify_access_docker","vendor":"ibm"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"IBM Security Verify Access 10.0.0.0, 10.0.1.0, 10.0.2.0, 10.0.3.0, and10.0.4.0 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:  233576.","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 Security Verify Access HOST header injection","id":"CVE-2022-36775","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:security_verify_access","products":["ibm:security_verify_access"],"type":"other","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in Cloud Pak for Security","id":"CVE-2022-36776"},"packages":[],"prev":{"headline":"Security feature bypass in Robotic Process Automation","id":"CVE-2022-36774"},"products":["Security Verify Access "],"published":"2023-02-17","related":[{"cvss_score":9.8,"headline":"Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-78401","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":9.8,"headline":"Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-78406","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":9.8,"headline":"IBM Security Verify Access Appliance command execution","id":"CVE-2024-49803","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2021-39070","kev_date_added":null,"published":"2022-02-02"},{"cvss_score":9.4,"headline":"IBM Security Verify Access Appliance hard coded credentials","id":"CVE-2024-49805","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.4,"headline":"IBM Security Verify Access Appliance hard coded credentials","id":"CVE-2024-49806","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.3,"headline":"Security Vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-1346","kev_date_added":null,"published":"2026-04-08"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-12","vendors":["IBM"]},"summary":"Attackers can inject HTTP headers to enable XSS, cache poisoning, or session hijacking in IBM Security Verify Access.","url":"https://insights.sbomify.com/CVE-2022-36775/"}