{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-4283 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-4283 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-4283 is a medium-severity vulnerability in IBM Security Information Queue, published on 2 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-4283 and fix it if it is affected.\n\nWhat it is: CVE-2020-4283 is a medium-severity vulnerability in IBM Security Information Queue, published on 2 Mar 2020. 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-2020-4283 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-4283/ (Markdown: https://insights.sbomify.com/CVE-2020-4283/index.md)","id":"CVE-2020-4283","markdown":"https://insights.sbomify.com/CVE-2020-4283/index.md","name":"CVE-2020-4283","record":{"aliases":["GHSA-p9wc-6qg4-wxc8"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Security Information Queue","requires_auth":"none","summary":"Hard-coded credentials in IBM Security 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_information_queue","vendor":"ibm"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/PR:N/C:H/S:C/A:N/I:N/UI:N/AC:H/RC:C/RL:O/E:U","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"IBM Security Information Queue (ISIQ) 1.0.0, 1.0.1, 1.0.2, 1.0.3, and 1.0.4 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: 176206.","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 Information Queue","id":"CVE-2020-4283","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Security Information Queue","id":"CVE-2020-4284"},"packages":[],"prev":{"headline":"Security feature bypass in Security Information Queue","id":"CVE-2020-4282"},"products":["Security Information Queue"],"published":"2020-03-02","related":[{"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-17","vendors":["IBM"]},"summary":"Hard-coded credentials in IBM Security Information Queue allow attackers to bypass authentication and access sensitive data.","url":"https://insights.sbomify.com/CVE-2020-4283/"}