{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-50326 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-50326 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-50326 is a high-severity vulnerability in IBM PowerSC, published on 2 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-50326 and fix it if it is affected.\n\nWhat it is: CVE-2023-50326 is a high-severity vulnerability in IBM PowerSC, published on 2 Feb 2024. 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-2023-50326 in the wild and no public exploit code.\n\nAffected product: IBM PowerSC. 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-2023-50326/ (Markdown: https://insights.sbomify.com/CVE-2023-50326/index.md)","id":"CVE-2023-50326","markdown":"https://insights.sbomify.com/CVE-2023-50326/index.md","name":"CVE-2023-50326","record":{"aliases":["GHSA-hh96-8ff8-hwhp"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM PowerSC","requires_auth":"none","summary":"Inadequate account lockout settings in IBM PowerSC allow remote attackers to brute force credentials and potentially take over accounts.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"powersc","vendor":"ibm"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"IBM PowerSC 1.3, 2.0, and 2.1 uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials.  IBM X-Force ID:  275107.","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 PowerSC information Disclosure","id":"CVE-2023-50326","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"IBM PowerSC weak security","id":"CVE-2023-50327"},"packages":[],"prev":{"headline":"IBM Cognos Command Center information disclosure","id":"CVE-2023-50324"},"products":["PowerSC"],"published":"2024-02-02","related":[{"cvss_score":6.5,"headline":"IBM PowerSC forced browsing","id":"CVE-2023-50935","kev_date_added":null,"published":"2024-02-02"},{"cvss_score":6.5,"headline":"IBM PowerSC clickjacking","id":"CVE-2023-50938","kev_date_added":null,"published":"2024-02-02"},{"cvss_score":6.3,"headline":"IBM PowerSC session fixation","id":"CVE-2023-50936","kev_date_added":null,"published":"2024-02-02"},{"cvss_score":6.3,"headline":"IBM PowerSC session fixation","id":"CVE-2023-50941","kev_date_added":null,"published":"2024-02-02"},{"cvss_score":6.1,"headline":"IBM PowerSC HTML injection","id":"CVE-2023-50933","kev_date_added":null,"published":"2024-02-02"},{"cvss_score":5.9,"headline":"IBM PowerSC information disclosure","id":"CVE-2023-50937","kev_date_added":null,"published":"2024-02-02"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["IBM"]},"summary":"Inadequate account lockout settings in IBM PowerSC allow remote attackers to brute force credentials and potentially take over accounts.","url":"https://insights.sbomify.com/CVE-2023-50326/"}