{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-36647 exists.","fix":"No fix has been published for CVE-2023-36647 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-36647 is a high-severity vulnerability in n/a, published on 12 Dec 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-36647 and fix it if it is affected.\n\nWhat it is: CVE-2023-36647 is a high-severity vulnerability in n/a, published on 12 Dec 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-36647 exists.\n\nAffected product: n/a. 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-36647/ (Markdown: https://insights.sbomify.com/CVE-2023-36647/index.md)","id":"CVE-2023-36647","markdown":"https://insights.sbomify.com/CVE-2023-36647/index.md","name":"CVE-2023-36647","record":{"aliases":["GHSA-8vmp-8f6c-x5hr"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"CryptoSpike security software","requires_auth":"none","summary":"Remote attackers can impersonate users and escalate privileges in ProLion CryptoSpike by exploiting a hard-coded JWT signing key.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cryptospike","vendor":"prolion"}],"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-798","name":"Use of Hard-coded Credentials"}],"description":"A hard-coded cryptographic private key used to sign JWT authentication tokens in ProLion CryptoSpike 3.0.15P2 allows remote attackers to impersonate arbitrary users and roles in web management and REST API endpoints via crafted JWT tokens.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2023-36647","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2023-36648"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2023-36646"},"products":["n/a"],"published":"2023-12-12","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2023-36655","kev_date_added":null,"published":"2023-12-06"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2023-36649","kev_date_added":null,"published":"2023-12-12"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2023-36646","kev_date_added":null,"published":"2023-12-11"},{"cvss_score":8.2,"headline":"Missing authorization in n/a","id":"CVE-2023-36648","kev_date_added":null,"published":"2023-12-12"},{"cvss_score":7.2,"headline":"Code injection in n/a","id":"CVE-2023-36650","kev_date_added":null,"published":"2023-12-12"},{"cvss_score":7.2,"headline":"Hardcoded credentials in n/a","id":"CVE-2023-36651","kev_date_added":null,"published":"2023-12-12"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-26","vendors":["n/a"]},"summary":"Remote attackers can impersonate users and escalate privileges in ProLion CryptoSpike by exploiting a hard-coded JWT signing key.","url":"https://insights.sbomify.com/CVE-2023-36647/"}