{"answers":{"affected":"2 open source packages ship an affected version, including com.usthe.sureness:sureness-core. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31581 exists.","fix":"Upgrade com.usthe.sureness:sureness-core to 1.0.8 or later.","what":"CVE-2023-31581 is a critical vulnerability in n/a, published on 24 Oct 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-31581 and fix it if it is affected.\n\nWhat it is: CVE-2023-31581 is a critical vulnerability in n/a, published on 24 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31581 exists.\n\nAffected packages and fixed versions:\n- com.usthe.sureness:sureness-core (Maven): affected all versions; fixed in 1.0.8\n- com.usthe.sureness:sureness-core (Maven): affected all versions; fixed in 1.0.8\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-31581/ (Markdown: https://insights.sbomify.com/CVE-2023-31581/index.md)","id":"CVE-2023-31581","markdown":"https://insights.sbomify.com/CVE-2023-31581/index.md","name":"CVE-2023-31581","record":{"aliases":["GHSA-3j2f-58rq-g6p7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Java security library","requires_auth":"none","summary":"An attacker can exploit a hardcoded key in the Sureness authentication library to bypass security controls and potentially take over accounts.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sureness","vendor":"dromara"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Dromara Sureness before v1.0.8 was discovered to use a hardcoded key.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Sureness uses hardcoded key","id":"CVE-2023-31581","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"jose4j uses weak cryptographic algorithm","id":"CVE-2023-31582"},"packages":[{"ecosystem":"Maven","fixed":["1.0.8"],"introduced":["0"],"last_affected":[],"package":"com.usthe.sureness:sureness-core","purl":null,"source":"GHSA-3j2f-58rq-g6p7"},{"ecosystem":"Maven","fixed":["1.0.8"],"introduced":["0"],"last_affected":[],"package":"com.usthe.sureness:sureness-core","purl":"pkg:maven/com.usthe.sureness/sureness-core","source":"GHSA-3j2f-58rq-g6p7"}],"prev":{"headline":"light-oauth2 missing public key verification","id":"CVE-2023-31580"},"products":["n/a"],"published":"2023-10-24","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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"An attacker can exploit a hardcoded key in the Sureness authentication library to bypass security controls and potentially take over accounts.","url":"https://insights.sbomify.com/CVE-2023-31581/"}