{"answers":{"affected":"2 open source packages ship an affected version, including codeigniter4/shield. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-27580 in the wild and no public exploit code.","fix":"Upgrade codeigniter4/shield to 1.0.0-beta.4 or later.","what":"CVE-2023-27580 is a high-severity vulnerability in codeigniter4 shield, published on 13 Mar 2023. 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-27580 and fix it if it is affected.\n\nWhat it is: CVE-2023-27580 is a high-severity vulnerability in codeigniter4 shield, published on 13 Mar 2023. 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-27580 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- codeigniter4/shield (Packagist): affected all versions; fixed in 1.0.0-beta.4\n- codeigniter4/shield (Packagist): affected all versions; fixed in 1.0.0-beta.4\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-27580/ (Markdown: https://insights.sbomify.com/CVE-2023-27580/index.md)","id":"CVE-2023-27580","markdown":"https://insights.sbomify.com/CVE-2023-27580/index.md","name":"CVE-2023-27580","record":{"aliases":["GHSA-c5vj-f36q-p9vg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"CodeIgniter Shield","requires_auth":"none","summary":"Attackers can easily crack user passwords if they obtain the unsalted SHA-384 hash, compromising user accounts in CodeIgniter Shield.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"shield","vendor":"codeigniter"}],"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-916","name":"Use of Password Hash With Insufficient Computational Effort"}],"description":"CodeIgniter Shield provides authentication and authorization for the CodeIgniter 4 PHP framework. An improper implementation was found in the password storage process. All hashed passwords stored in Shield v1.0.0-beta.3 or earlier are easier to crack than expected due to the vulnerability. Therefore, they should be removed as soon as possible. If an attacker gets (1) the user's hashed password by Shield, and (2) the hashed password (SHA-384 hash without salt) from somewhere, the attacker may easily crack the user's password. Upgrade to Shield v1.0.0-beta.4 or later to fix this issue. After upgrading, all users’ hashed passwords should be updated (saved to the database). There are no known workarounds.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"CodeIgniter Shield Password Shucking Vulnerability","id":"CVE-2023-27580","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"weak_cryptography","year":"2023"},"n_packages":2,"n_references":6,"next":{"headline":"github-slug-action vulnerable to arbitrary code execution","id":"CVE-2023-27581"},"packages":[{"ecosystem":"Packagist","fixed":["1.0.0-beta.4"],"introduced":["0"],"last_affected":[],"package":"codeigniter4/shield","purl":null,"source":"GHSA-c5vj-f36q-p9vg"},{"ecosystem":"Packagist","fixed":["1.0.0-beta.4"],"introduced":["0"],"last_affected":[],"package":"codeigniter4/shield","purl":"pkg:composer/codeigniter4/shield","source":"GHSA-c5vj-f36q-p9vg"}],"prev":{"headline":"TensorFlow has Floating Point Exception in TFLite in conv kernel","id":"CVE-2023-27579"},"products":["shield"],"published":"2023-03-13","related":[{"cvss_score":5,"headline":"Cleartext Storage of Sensitive Information in codeigniter4/shield","id":"CVE-2023-48707","kev_date_added":null,"published":"2023-11-24"},{"cvss_score":5,"headline":"Insertion of Sensitive Information into Log in codeigniter4/shield","id":"CVE-2023-48708","kev_date_added":null,"published":"2023-11-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"2025-02-25","vendors":["codeigniter4"]},"summary":"Attackers can easily crack user passwords if they obtain the unsalted SHA-384 hash, compromising user accounts in CodeIgniter Shield.","url":"https://insights.sbomify.com/CVE-2023-27580/"}