{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-20409 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-20409 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-20409 is a medium-severity vulnerability in IBM Security Verify Information Queue, published on 12 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-20409 and fix it if it is affected.\n\nWhat it is: CVE-2021-20409 is a medium-severity vulnerability in IBM Security Verify Information Queue, published on 12 Feb 2021. 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-2021-20409 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-2021-20409/ (Markdown: https://insights.sbomify.com/CVE-2021-20409/index.md)","id":"CVE-2021-20409","markdown":"https://insights.sbomify.com/CVE-2021-20409/index.md","name":"CVE-2021-20409","record":{"aliases":["GHSA-8wfg-3q96-w9rf"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Security Verify","requires_auth":"none","summary":"Remote attackers can intercept sensitive data via man-in-the-middle attacks due to missing HTTP Strict Transport Security headers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_verify_information_queue","vendor":"ibm"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"IBM Security Verify Information Queue 1.0.6 and 1.0.7 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: 196188.","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 Information Queue information disclosure","id":"CVE-2021-20409","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Security Verify Information Queue","id":"CVE-2021-20410"},"packages":[],"prev":{"headline":"Information disclosure in Security Verify Information Queue","id":"CVE-2021-20408"},"products":["Security Verify Information Queue"],"published":"2021-02-12","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.8,"headline":"Hardcoded credentials in Security Verify Information Queue","id":"CVE-2022-35287","kev_date_added":null,"published":"2022-07-25"},{"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":"Remote attackers can intercept sensitive data via man-in-the-middle attacks due to missing HTTP Strict Transport Security headers.","url":"https://insights.sbomify.com/CVE-2021-20409/"}