{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-4282 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-4282 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-4282 is a low-severity vulnerability in IBM Security Information Queue, published on 8 Apr 2020. 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-2020-4282 and fix it if it is affected.\n\nWhat it is: CVE-2020-4282 is a low-severity vulnerability in IBM Security Information Queue, published on 8 Apr 2020. 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-2020-4282 in the wild and no public exploit code.\n\nAffected product: IBM Security 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-2020-4282/ (Markdown: https://insights.sbomify.com/CVE-2020-4282/index.md)","id":"CVE-2020-4282","markdown":"https://insights.sbomify.com/CVE-2020-4282/index.md","name":"CVE-2020-4282","record":{"aliases":["GHSA-6v82-qq9q-vcc9"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Security Information Queue","requires_auth":"low_privilege","summary":"Authenticated users can bypass character restrictions to perform unauthorized actions in IBM Security Information Queue.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_information_queue","vendor":"ibm"}],"cvss":{"score":3,"severity":"low","source":"cna","vector":"CVSS:3.0/AV:N/A:N/UI:R/AC:H/I:L/PR:L/C:N/S:C/RL:O/RC:C/E:U","version":"3.0"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"IBM Security Information Queue (ISIQ) 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, and 1.0.5 could allow an authenticated user to perform unauthorized actions by bypassing illegal character restrictions. X-Force ID: 176205.","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":"Security feature bypass in Security Information Queue","id":"CVE-2020-4282","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in Security Information Queue","id":"CVE-2020-4283"},"packages":[],"prev":{"headline":"Cross-site scripting in Rational DOORS Next Generation","id":"CVE-2020-4281"},"products":["Security Information Queue"],"published":"2020-04-08","related":[{"cvss_score":6.8,"headline":"Hardcoded credentials in Security Information Queue","id":"CVE-2020-4283","kev_date_added":null,"published":"2020-03-02"},{"cvss_score":6.1,"headline":"Cross-site scripting in Security Information Queue","id":"CVE-2019-4217","kev_date_added":null,"published":"2019-06-06"},{"cvss_score":5.9,"headline":"Security feature bypass in Security Information Queue","id":"CVE-2019-4162","kev_date_added":null,"published":"2019-06-06"},{"cvss_score":5.3,"headline":"Information disclosure in Security Information Queue","id":"CVE-2020-4284","kev_date_added":null,"published":"2020-04-08"},{"cvss_score":5.3,"headline":"Information disclosure in Security Information Queue","id":"CVE-2020-4289","kev_date_added":null,"published":"2020-04-08"},{"cvss_score":4.7,"headline":"Information disclosure in Security Information Queue","id":"CVE-2020-4291","kev_date_added":null,"published":"2020-04-08"},{"cvss_score":4.3,"headline":"Information disclosure in Security Information Queue","id":"CVE-2019-4219","kev_date_added":null,"published":"2019-06-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["IBM"]},"summary":"Authenticated users can bypass character restrictions to perform unauthorized actions in IBM Security Information Queue.","url":"https://insights.sbomify.com/CVE-2020-4282/"}