{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-22377 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22377 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22377 is a medium-severity vulnerability in IBM Security Verify Privilege, published on 17 Oct 2023. 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-22377 and fix it if it is affected.\n\nWhat it is: CVE-2022-22377 is a medium-severity vulnerability in IBM Security Verify Privilege, published on 17 Oct 2023. 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-22377 in the wild and no public exploit code.\n\nAffected product: IBM Security Verify Privilege. 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-22377/ (Markdown: https://insights.sbomify.com/CVE-2022-22377/index.md)","id":"CVE-2022-22377","markdown":"https://insights.sbomify.com/CVE-2022-22377/index.md","name":"CVE-2022-22377","record":{"aliases":["GHSA-jm5q-9m8m-p5p5"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Security Verify Privilege","requires_auth":"none","summary":"Remote attackers can obtain sensitive information via man-in-the-middle attacks due to missing HTTP Strict Transport Security in IBM Security Verify Privilege.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_verify_privilege_on-premises","vendor":"ibm"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"IBM Security Verify Privilege On-Premises 11.5 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. An attacker could exploit this vulnerability to obtain sensitive information using man in the middle techniques.  IBM X-Force ID:  221827.","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 Privilege information disclosure","id":"CVE-2022-22377","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"IBM Security Verify Privilege improper authentication","id":"CVE-2022-22380"},"packages":[],"prev":{"headline":"IBM Security Verify Privilege command execution","id":"CVE-2022-22375"},"products":["Security Verify Privilege"],"published":"2023-10-17","related":[{"cvss_score":7.5,"headline":"IBM Security Verify Privilege information disclosure","id":"CVE-2024-31887","kev_date_added":null,"published":"2024-04-16"},{"cvss_score":7.2,"headline":"IBM Security Verify Privilege command execution","id":"CVE-2022-22375","kev_date_added":null,"published":"2023-10-17"},{"cvss_score":6.5,"headline":"IBM Security Verify Privilege improper input validation","id":"CVE-2021-29913","kev_date_added":null,"published":"2023-10-17"},{"cvss_score":5.9,"headline":"IBM Security Verify Privilege information disclosure","id":"CVE-2022-22385","kev_date_added":null,"published":"2023-10-17"},{"cvss_score":5.3,"headline":"IBM Security Verify Privilege On-Premises information disclosure","id":"CVE-2022-43890","kev_date_added":null,"published":"2024-03-04"},{"cvss_score":5.3,"headline":"IBM Security Verify Privilege information disclosure","id":"CVE-2021-20581","kev_date_added":null,"published":"2023-10-17"}],"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":"2024-09-13","vendors":["IBM"]},"summary":"Remote attackers can obtain sensitive information via man-in-the-middle attacks due to missing HTTP Strict Transport Security in IBM Security Verify Privilege.","url":"https://insights.sbomify.com/CVE-2022-22377/"}