{"uuid": "9ea51bbe-b845-48a8-8db0-cfe99b73f14d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-22963", "type": "published-proof-of-concept", "source": "https://t.me/tech_b0lt_Genona/3068", "content": "\u041e\u043f\u044f\u0442\u044c \"\u0437\u0435\u0440\u043e\u0434\u0435\u0438\" \u0432 Java \u043f\u043e\u0434\u044a\u0435\u0445\u0430\u043b\u0438. \u0412\u043f\u0440\u043e\u0447\u0435\u043c \u043d\u0438\u0447\u0435\u0433\u043e \u043d\u043e\u0432\u043e\u0433\u043e.\n\nAs we have already reported the unconfirmed critical vulnerability in the Spring core, leads to remote code execution. We named the vulnerability Spring4Shell because this is something like Log4Shell, actually it is more effective than Log4Shell. \n\nSpring4Shell Details and Exploit code leaked\nhttps://www.cyberkendra.com/2022/03/spring4shell-details-and-exploit-code.html\n+\nPoC\nhttps://github.com/dinosn/CVE-2022-22963/blob/main/poc.py", "creation_timestamp": "2022-03-30T21:49:13.000000Z"}