{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-35287 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-35287 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-35287 is a medium-severity vulnerability in IBM Security Verify Information Queue, published on 25 Jul 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-35287 and fix it if it is affected.\n\nWhat it is: CVE-2022-35287 is a medium-severity vulnerability in IBM Security Verify Information Queue, published on 25 Jul 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-35287 in the wild and no public exploit code.\n\nAffected product: IBM Security Verify Information Queue. 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-35287/ (Markdown: https://insights.sbomify.com/CVE-2022-35287/index.md)","id":"CVE-2022-35287","markdown":"https://insights.sbomify.com/CVE-2022-35287/index.md","name":"CVE-2022-35287","record":{"aliases":["GHSA-hhh6-m9cr-q5p4"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Security Verify","requires_auth":"none","summary":"Hard-coded credentials in IBM Security Verify Information Queue allow attackers to bypass authentication and access sensitive data.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_verify_information_queue","vendor":"ibm"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.0/PR:N/UI:N/A:N/I:N/C:H/AV:N/AC:H/S:C/E:U/RL:O/RC:C","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"IBM Security Verify Information Queue 10.0.2 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. IBM X-Force ID: 230817.","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":"Hardcoded credentials in Security Verify Information Queue","id":"CVE-2022-35287","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Security Verify Information Queue","id":"CVE-2022-35288"},"packages":[],"prev":{"headline":"Cross-site request forgery in Security Verify Information Queue","id":"CVE-2022-35286"},"products":["Security Verify Information Queue"],"published":"2022-07-25","related":[{"cvss_score":7.5,"headline":"Auth bypass in Security Verify Information Queue","id":"CVE-2021-20411","kev_date_added":null,"published":"2021-02-12"},{"cvss_score":7.1,"headline":"Information disclosure in Security Verify Information Queue","id":"CVE-2021-20408","kev_date_added":null,"published":"2021-02-12"},{"cvss_score":6.5,"headline":"IBM Security Verify Information Queue denial of service","id":"CVE-2024-45669","kev_date_added":null,"published":"2025-09-10"},{"cvss_score":6.5,"headline":"Cross-site request forgery in Security Verify Information Queue","id":"CVE-2022-35285","kev_date_added":null,"published":"2022-07-25"},{"cvss_score":6.5,"headline":"Denial of service in Security Verify Information Queue","id":"CVE-2022-35283","kev_date_added":null,"published":"2022-07-14"},{"cvss_score":6.4,"headline":"IBM Security Verify Information Queue code execution","id":"CVE-2024-47120","kev_date_added":null,"published":"2025-09-10"}],"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":"Hard-coded credentials in IBM Security Verify Information Queue allow attackers to bypass authentication and access sensitive data.","url":"https://insights.sbomify.com/CVE-2022-35287/"}