{"answers":{"affected":"2 open source packages ship an affected version, including gree/jose. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-5431 in the wild and no public exploit code.","fix":"Upgrade gree/jose to 2.2.1 or later.","what":"CVE-2016-5431 is a high-severity vulnerability in jose-php, published on 7 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-5431 and fix it if it is affected.\n\nWhat it is: CVE-2016-5431 is a high-severity vulnerability in jose-php, published on 7 Aug 2019. 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-2016-5431 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gree/jose (Packagist): affected all versions; fixed in 2.2.1\n- gree/jose (Packagist): affected all versions; fixed in 2.2.1\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-2016-5431/ (Markdown: https://insights.sbomify.com/CVE-2016-5431/index.md)","id":"CVE-2016-5431","markdown":"https://insights.sbomify.com/CVE-2016-5431/index.md","name":"CVE-2016-5431","record":{"aliases":["GHSA-xm5f-hc9r-76f3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP JOSE library","requires_auth":"none","summary":"Attackers can bypass JWS signature verification in the PHP JOSE library by exploiting key confusion, allowing them to forge valid tokens.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"php_jose","vendor":"php_jose_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"The PHP JOSE Library by Gree Inc. before version 2.2.1 is vulnerable to key confusion/algorithm substitution in the JWS component resulting in bypassing the signature verification via crafted tokens.","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":"PHP JOSE Library by Gree Inc. Uses a Broken or Risky Cryptographic Algorithm","id":"CVE-2016-5431","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"security_feature_bypass","year":"2016"},"n_packages":2,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2016-5432"},"packages":[{"ecosystem":"Packagist","fixed":["2.2.1"],"introduced":["0"],"last_affected":[],"package":"gree/jose","purl":null,"source":"GHSA-xm5f-hc9r-76f3"},{"ecosystem":"Packagist","fixed":["2.2.1"],"introduced":["0"],"last_affected":[],"package":"gree/jose","purl":"pkg:composer/gree/jose","source":"GHSA-xm5f-hc9r-76f3"}],"prev":{"headline":"The RSA 1.5 algorithm implementation in the JOSE_JWE class in JWE.php in jose-php before 2.2.1 lacks the Random Filling protection mechanism","id":"CVE-2016-5430"},"products":["jose-php"],"published":"2019-08-07","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Attackers can bypass JWS signature verification in the PHP JOSE library by exploiting key confusion, allowing them to forge valid tokens.","url":"https://insights.sbomify.com/CVE-2016-5431/"}