{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55556 exists.","fix":"No fix has been published for CVE-2024-55556 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-55556 is a critical unsafe deserialization vulnerability in n/a, published on 7 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-55556 and fix it if it is affected.\n\nWhat it is: CVE-2024-55556 is a critical unsafe deserialization vulnerability in n/a, published on 7 Jan 2025. 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-2024-55556 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-2024-55556/ (Markdown: https://insights.sbomify.com/CVE-2024-55556/index.md)","id":"CVE-2024-55556","markdown":"https://insights.sbomify.com/CVE-2024-55556/index.md","name":"CVE-2024-55556","record":{"aliases":["GHSA-gxfw-pm97-x2qf"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Crater Invoice","requires_auth":"none","summary":"An attacker with the APP_KEY can achieve remote code execution in Crater Invoice by manipulating encrypted session cookies to trigger unsafe deserialization.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","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-502","name":"Deserialization of Untrusted Data"}],"description":"A vulnerability in Crater Invoice allows an unauthenticated attacker with knowledge of the APP_KEY to achieve remote command execution on the server by manipulating the laravel_session cookie, exploiting arbitrary deserialization through the encrypted session data. The exploitation vector of this vulnerability relies on an attacker obtaining Laravel's secret APP_KEY, which would allow them to decrypt and manipulate session cookies (laravel_session) containing serialized data. By altering this data and re-encrypting it with the APP_KEY, the attacker could trigger arbitrary deserialization on the server, potentially leading to remote command execution (RCE). The vulnerability is primarily exploited by accessing an exposed cookie and manipulating it using the secret key to gain malicious access to the server.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-12-13","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2024-12-13","kind":"metasploit","ref":"exploit/linux/http/invoiceshelf_unauth_rce_cve_2024_55556","stars":null,"title":"InvoiceShelf unauthenticated PHP Deserialization Vulnerability"}],"tier":"weaponised"},"has_fix":null,"headline":"Deserialization in n/a","id":"CVE-2024-55556","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2024-55557"},"packages":[],"prev":{"headline":"Deserialization in n/a","id":"CVE-2024-55555"},"products":["n/a"],"published":"2025-01-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-08","vendors":["n/a"]},"summary":"An attacker with the APP_KEY can achieve remote code execution in Crater Invoice by manipulating encrypted session cookies to trigger unsafe deserialization.","url":"https://insights.sbomify.com/CVE-2024-55556/"}