{"uuid": "4e02e1e7-05b5-4e27-9fe3-ceffab814423", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-55555", "type": "seen", "source": "https://t.me/cvedetector/14582", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-55555 - Invoice Ninja Laravel RCE\", \n  \"Content\": \"CVE ID : CVE-2024-55555 \nPublished : Jan. 7, 2025, 5:15 p.m. | 31\u00a0minutes ago \nDescription : Invoice Ninja before 5.10.43 allows remote code execution from a pre-authenticated route when an attacker knows the APP_KEY. This is exacerbated by .env files, available from the product's repository, that have default APP_KEY values. The route/{hash} route defined in the invoiceninja/routes/client.php file can be accessed without authentication. The parameter {hash} is passed to the function decrypt that expects a Laravel ciphered value containing a serialized object. (Furthermore, Laravel contains several gadget chains usable to trigger remote command execution from arbitrary deserialization.) Therefore, an attacker in possession of the APP_KEY is able to fully control a string passed to an unserialize function. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-07T18:54:11.000000Z"}