{"vulnerability": "CVE-2022-42905", "sightings": [{"uuid": "31dc6bc2-6b2f-4234-8ef9-e5a1e995a752", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-42905", "type": "seen", "source": "https://t.me/tech_b0lt_Genona/3521", "content": "\u0412 \u0431\u043b\u043e\u0433\u0435 Trail of Bits \u0432\u044b\u0448\u043b\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \"Keeping the wolves out of wolfSSL\". \u0422\u0430\u043a \u043a\u0430\u043a \u0443 \u043c\u0435\u043d\u044f \u0431\u044b\u043b \u0443\u0436\u0435 \u043d\u0430 \u0431\u043b\u0438\u0436\u0430\u0439\u0448\u0435\u0435 \u0432\u0440\u0435\u043c\u044f \u0437\u0430\u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0430\u043d \u043f\u043e\u0441\u0442 \u043e \u0444\u0430\u0437\u0437\u0435\u0440\u0430\u0445 \u0441\u0435\u0442\u0435\u0432\u044b\u0445 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432, \u0442\u043e \u0434\u0443\u043c\u0430\u043b \u0437\u0430\u043a\u0438\u043d\u0443\u0442\u044c \u0441\u0442\u0430\u0442\u044c\u044e \u0432 \u0441\u043f\u0438\u0441\u043e\u043a \u043d\u0430 \u0447\u0442\u0435\u043d\u0438\u0435 \"Someday\", \u043d\u043e \u0447\u0442\u043e-\u0442\u043e \u043f\u043e\u0432\u0435\u043b\u0435\u043b\u043e \u043c\u043d\u0435 \u043f\u0440\u043e\u0447\u0438\u0442\u0430\u0442\u044c \u0435\u0451...\n\n\u041f\u043e \u0441\u0443\u0442\u0438 \u0432 \u0441\u0442\u0430\u0442\u044c\u0435 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u043e \u043d\u043e\u0432\u043e\u043c \u0444\u0430\u0437\u0437\u0435\u0440\u0435 tlspuffin \u043d\u0430 \u043c\u043e\u0434\u043d\u043e\u043c Rust. \u041d\u043e \u043e\u043d \u043e\u043a\u0430\u0437\u0430\u043b\u0441\u044f \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c \u0438 \u0435\u0433\u043e \u0446\u0435\u043b\u0438 \u044d\u0442\u043e \u043a\u0440\u0438\u043f\u0442\u043e\u0433\u0440\u0430\u0444\u0438\u0447\u0435\u0441\u043a\u0438\u0435 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u044b. tlspuffin \u0431\u0430\u0437\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u043d\u0430 \u043c\u043e\u0434\u0435\u043b\u0438 \u0443\u0433\u0440\u043e\u0437 \u0414\u043e\u043b\u0435\u0432\u0430-\u042f\u043e \u0438 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0430\u043d \u043f\u043e \u043f\u0440\u0430\u0432\u0438\u043b\u0430\u043c LibAFL (\u043d\u0430 \u0441\u043a\u0440\u0438\u043d\u0448\u043e\u0442\u0435 \u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0430 tlspuffin). \u0414\u0430, \u0434\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u043f\u043e\u0434\u043e\u0431\u043d\u044b\u0445 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0442 ProVerif \u0438 Tamarin, \u043d\u043e \u043f\u043e\u0434\u043e\u0431\u043d\u044b\u0439 \u0444\u0430\u0437\u0437\u0435\u0440 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u043d\u0430\u0439\u0442\u0438 \u043b\u043e\u0433\u0438\u0447\u0435\u0441\u043a\u0438\u0435 \u0431\u0430\u0433\u0438 \u043f\u0440\u0438 \u0441\u043b\u043e\u0436\u043d\u043e \u0443\u043b\u043e\u0432\u0438\u043c\u044b\u0445 \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u044f\u0445\n\n\u0414\u043b\u044f \u043f\u0435\u0440\u0432\u043e\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u0442\u0435\u0441\u0442\u0430 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442 \u043f\u0435\u0440\u0435\u043d\u0430\u0448\u0451\u043b, \u043d\u0430\u0439\u0434\u0435\u043d\u043d\u044b\u0435 Trail of Bits \u0440\u0430\u043d\u0435\u0435, \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 CVE-2022-25640 and CVE-2022-25638 \u0432 wolfSSL, \u0430 \u0437\u0430\u0442\u0435\u043c \u0441\u043c\u043e\u0433 \u043d\u0430\u0439\u0442\u0438 \u043d\u043e\u0432\u044b\u0435 (\u043f\u0440\u043e\u0446\u0435\u0441\u0441 \u0444\u0430\u0437\u0437\u0438\u043d\u0433\u0430 \u0432 \u0441\u0440\u0435\u0434\u043d\u0435\u043c \u0437\u0430\u043d\u044f\u043b \u043e\u043a\u043e\u043b\u043e \u0447\u0430\u0441\u0430 \u043d\u0430 \u043a\u0430\u0436\u0434\u0443\u044e \u0438\u0437 \u043d\u0438\u0445):\n\n- DOSC (Denial of service against clients): CVE-2022-38153\n- DOSS (Denial of service against servers): CVE-2022-38152\n- BUF: CVE-2022-39173\n- HEAP: CVE-2022-42905\n\n\u041a\u0430\u043a \u043f\u0438\u0448\u0435\u0442 \u0430\u0432\u0442\u043e\u0440, \u0432 \u0441\u043b\u0443\u0447\u0430\u0435 \u043f\u0435\u0440\u0432\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0434\u043b\u044f \u0432\u043e\u0441\u043f\u0440\u043e\u0438\u0437\u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0431\u0430\u0433\u0438 \u043f\u043e\u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043b\u043e\u0441\u044c \u0431\u044b \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u044f \u043e\u043a\u043e\u043b\u043e 30 \u0440\u0430\u0437\u043d\u044b\u0445 \u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u0439. \u041d\u043e \u044d\u0442\u043e\u0433\u043e \u043d\u0435 \u043f\u043e\u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043b\u043e\u0441\u044c, \u0442\u0430\u043a \u043a\u0430\u043a tlspuffin \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0432\u043e\u0441\u0441\u043e\u0437\u0434\u0430\u0442\u044c \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e\u0435 \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0435 \u0438 \u0437\u0430\u0442\u0435\u043c \u043f\u0440\u043e\u0430\u043d\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u0442\u044c \u0432 GDB. \u041f\u0440\u0438\u0447\u0438\u043d\u043e\u0439 \u0431\u0430\u0433\u0438 \u043e\u043a\u0430\u0437\u0430\u043b\u043e\u0441\u044c \u043d\u0430\u043b\u0438\u0447\u0438\u0435 \u043d\u0435\u043a\u043e\u0435\u0433\u043e \u0433\u043b\u043e\u0431\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u043e\u0431\u0449\u0435\u0433\u043e \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u044f \u043c\u0435\u0436\u0434\u0443 \u043a\u043b\u0438\u0435\u043d\u0442\u0430\u043c\u0438, \u0447\u0442\u043e \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u0443\u0434\u0438\u0432\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u0434\u043b\u044f \u0442\u0430\u043a\u043e\u0439 \u0431\u0438\u0431\u043b\u0438\u043e\u0442\u0435\u043a\u0438.\n\n\u0418\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441 tlspuffin \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0434\u043e\u0431\u0430\u0432\u0438\u0442\u044c \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u0438 \u0434\u043b\u044f \u0434\u0440\u0443\u0433\u0438\u0445 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432, \u0445\u043e\u0442\u044f \u044d\u0442\u043e \u043c\u043e\u0436\u0435\u0442 \u043f\u043e\u0442\u0440\u0435\u0431\u043e\u0432\u0430\u0442\u044c \u0437\u043d\u0430\u0447\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0435 \u043a\u043e\u043b\u0438\u0447\u0435\u0441\u0442\u0432\u043e \u0432\u0440\u0435\u043c\u0435\u043d\u0438. \u041a \u043f\u0440\u0438\u043c\u0435\u0440\u0443, \u0443 \u043a\u043e\u043c\u0430\u043d\u0434\u044b \u0443\u0448\u043b\u043e 5-6 \u043d\u0435\u0434\u0435\u043b\u044c \u043d\u0430 \u0434\u043e\u0431\u0430\u0432\u043b\u0435\u043d\u0438\u0435 SSH, \u043d\u043e \u0434\u043e\u0431\u0430\u0432\u0438\u0432 \u043e\u0434\u0438\u043d \u0440\u0430\u0437 \u044d\u0442\u043e \u043c\u043e\u0436\u043d\u043e \u0431\u0443\u0434\u0435\u0442 \u043f\u0435\u0440\u0435\u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c. \u0422\u0430\u043a tlspuffin \u043c\u043e\u0436\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0434\u043b\u044f \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u044f \u0442\u0435\u0441\u0442\u043e\u0432\u044b\u0445 \u043d\u0430\u0431\u043e\u0440\u043e\u0432, \u0430 \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u043f\u043e\u043b\u0443\u0447\u0435\u043d\u043d\u044b\u0445 \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u043e\u0432 \u043f\u0440\u043e\u0432\u043e\u0434\u0438\u0442\u044c \u0440\u0435\u0433\u0440\u0435\u0441\u0441\u0438\u043e\u043d\u043d\u044b\u0435 \u0442\u0435\u0441\u0442\u044b. \u0422\u043e \u0435\u0441\u0442\u044c \u043f\u043e \u0441\u0443\u0442\u0438 \u043c\u043e\u0436\u0435\u0442 \u0437\u0430\u043c\u0435\u043d\u0438\u0442\u044c TLS-Attacker\n\n\u041a\u0430\u043a \u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u043e \u0437\u0430\u043c\u0435\u0442\u0438\u043b\u0438 \u0430\u0432\u0442\u043e\u0440\u044b \u0432 \u0437\u0430\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u0438, TLS \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u044b, \u044d\u0442\u043e \u0442\u0430 \u043f\u043e\u0432\u0441\u0435\u0434\u043d\u0435\u0432\u043d\u0430\u044f \u0438 \u043f\u043e\u0432\u0441\u0435\u043c\u0435\u0441\u0442\u043d\u0430\u044f \u0432\u0435\u0449\u044c, \u043a\u043e\u0442\u043e\u0440\u043e\u0439 \u043c\u044b \"\u0434\u043e\u0432\u0435\u0440\u044f\u0435\u043c\" \u0438 \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0435\u0451 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u044c \u0434\u0435\u0439\u0441\u0442\u0432\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u0432\u0430\u0436\u043d\u0430\u044f \u0432\u0435\u0449\u044c", "creation_timestamp": "2023-01-17T10:37:08.000000Z"}, {"uuid": "57b32230-48b5-4a9d-aa94-930c080ca7c6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-42905", "type": "seen", "source": "https://t.me/arpsyndicate/3026", "content": "#ExploitObserverAlert\n\nCVE-2022-42905\n\nDESCRIPTION: Exploit Observer has 6 entries in 4 file formats related to CVE-2022-42905. In wolfSSL before 5.5.2, if callback functions are enabled (via the WOLFSSL_CALLBACKS flag), then a malicious TLS 1.3 client or network attacker can trigger a buffer over-read on the heap of 5 bytes. (WOLFSSL_CALLBACKS is only intended for debugging.)\n\nFIRST-EPSS: 0.001410000\nNVD-IS: 5.2\nNVD-ES: 3.9", "creation_timestamp": "2024-01-26T18:07:14.000000Z"}, {"uuid": "87752c65-16f4-45da-9f37-68c4904c6d09", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-42905", "type": "seen", "source": "https://t.me/cibsecurity/52577", "content": "\u203c CVE-2022-42905 \u203c\n\nIn wolfSSL before 5.5.2, if callback functions are enabled (via the WOLFSSL_CALLBACKS flag), then a malicious TLS 1.3 client or network attacker can trigger a buffer over-read on the heap of 5 bytes. (WOLFSSL_CALLBACKS is only intended for debugging.)\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-11-07T02:33:44.000000Z"}, {"uuid": "d2507e04-0bb8-4279-8bf6-156af6640fc4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-42905", "type": "seen", "source": "https://t.me/hacking_Attack/86320", "content": "Exploit Collector\nwolfSSL WOLFSSL_CALLBACKS Heap Buffer Over-Read\n\nhttps://3.bp.blogspot.com/-vLPaJ0bXchM/WWlvcii8AuI/AAAAAAAAIPY/lohzKYQrhRkUA5ocnA3xRTtIEj7YZIM-ACLcBGAs/s1600/h77.png \nwolfSSL versions prior to 5.5.2 suffer from a heap buffer over-read with WOLFSSL_CALLBACKS and can be triggered with a single Client Hello message.\n\nSHA-256 | 22c8bd75668677a45f903b9289dfd4de5cffd44e8f21af11820559278a985e59\n\nDownload\n# wolfSSL before 5.5.2: Heap-buffer over-read with WOLFSSL_CALLBACKS\n====================================================================\n\n## INFO\n=======\n\nThe CVE project has assigned the id CVE-2022-42905 to this issue.\n\nSeverity: 9.1 CRITICAL\nAffected version: before 5.5.2\nEnd of embargo: Ended October 28, 2022\nBlog Post: https://blog.trailofbits.com/2023/01/12/wolfssl-vulnerabilities-tlspuffin-fuzzing-ssh/\n\n## SUMMARY\n==========\n\nIf wolfSSL callback functions are enabled (i.e., the flag `WOLFSSL_CALLBACKS` is\nenabled), then a malicious client or network attacker can send a Client Hello\nmessage to a server that when parsed by the server will trigger a buffer\nover-read on the heap of at least 5 bytes. Similarly, a malicious server or a\nnetwork attacker can send a Hello Retry Request message to a client that when\nparsed by the client will trigger a buffer over-read on the heap of at least 15\nbytes.\n\nThe `AddPacketInfo` is given a buffer that should be the input buffer and that\nactually is shifted by 5 bytes on the left, i.e., instead of reading\n`input[0]..input[length]`, the function will read `input[-5]..input[length]` and\nstore it in a buffer that is exposed through the wolfSSL API. Note that `input`\nis stored on the heap and `input[-5]` to `input[-1]` might store sensitive data\nthat should not be given to `AddPacketInfo`, for example when callback functions\nare used as logging facility (through the API functions `wolfSSL_accept_ex` and\n`wolfSSL_connect_ex`).\n\nThis buffer over-read can be triggered at a server with a single Client Hello\nmessage. We have confirmed this with a proof-of-concept test case given below on\nwolfSSL 5.5.0, on the version from the master branch, and on version 5.4.0. A\nsimilar buffer over-read can be triggered at a client with the same wolfSSL\nversions.\n\n## DETAILS\n==========\n\n(Note: All code snippets and line numbers are with respect to the git hash\n`#43715d1bb5b8c5b8b18cba4be3171fd1dd7eb046` on remote\n`git@github.com:wolfssl/wolfssl.git`.)\n\nWhen executing the first proof of concept test case given below, we reach a call\nto `DoTls13HandShakeMsgType` from `tls13.c:DoTls13HandShakeMsg:10443` when the\nserver parses the Client Hello message, with the following values:\n\n```c\nsize = 16520;\ntotalSz = 16524;\n*inOutIdx = 4;\ntype = 1;\ninput; // buffer containing the input to be processed, before input,\nthere seems to be another input stored\n```\n\n`*inOutIdx=4` because of the call to `GetHandshakeHeader` at line\n`tls13.c:10411`.\n\nWe enter the function `tls13.c:DoTls13HandShakeMsgType` and because\n`WOLFSSL_CALLBACKS` flag is defined, we enter this snippet:\n\n```c\n#if defined(WOLFSSL_CALLBACKS)\n/* add name later, add on record and handshake header part back on */\nif (ssl->toInfoOn) {\nint add = RECORD_HEADER_SZ + HANDSHAKE_HEADER_SZ;\nAddPacketInfo(ssl, 0, handshake, input + *inOutIdx - add,\nsize + add, READ_PROTO, ssl->heap);\nAddLateRecordHeader(&ssl->curRL, &ssl->timeoutInfo);\n}", "creation_timestamp": "2026-09-01T20:01:05.899774Z"}, {"uuid": "1b3e811c-2716-4a7d-808d-194f23380c7e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-42905", "type": "seen", "source": "https://t.me/hacking_Attack/86320", "content": "Exploit Collector\nwolfSSL WOLFSSL_CALLBACKS Heap Buffer Over-Read\n\nhttps://3.bp.blogspot.com/-vLPaJ0bXchM/WWlvcii8AuI/AAAAAAAAIPY/lohzKYQrhRkUA5ocnA3xRTtIEj7YZIM-ACLcBGAs/s1600/h77.png \nwolfSSL versions prior to 5.5.2 suffer from a heap buffer over-read with WOLFSSL_CALLBACKS and can be triggered with a single Client Hello message.\n\nSHA-256 | 22c8bd75668677a45f903b9289dfd4de5cffd44e8f21af11820559278a985e59\n\nDownload\n# wolfSSL before 5.5.2: Heap-buffer over-read with WOLFSSL_CALLBACKS\n====================================================================\n\n## INFO\n=======\n\nThe CVE project has assigned the id CVE-2022-42905 to this issue.\n\nSeverity: 9.1 CRITICAL\nAffected version: before 5.5.2\nEnd of embargo: Ended October 28, 2022\nBlog Post: https://blog.trailofbits.com/2023/01/12/wolfssl-vulnerabilities-tlspuffin-fuzzing-ssh/\n\n## SUMMARY\n==========\n\nIf wolfSSL callback functions are enabled (i.e., the flag `WOLFSSL_CALLBACKS` is\nenabled), then a malicious client or network attacker can send a Client Hello\nmessage to a server that when parsed by the server will trigger a buffer\nover-read on the heap of at least 5 bytes. Similarly, a malicious server or a\nnetwork attacker can send a Hello Retry Request message to a client that when\nparsed by the client will trigger a buffer over-read on the heap of at least 15\nbytes.\n\nThe `AddPacketInfo` is given a buffer that should be the input buffer and that\nactually is shifted by 5 bytes on the left, i.e., instead of reading\n`input[0]..input[length]`, the function will read `input[-5]..input[length]` and\nstore it in a buffer that is exposed through the wolfSSL API. Note that `input`\nis stored on the heap and `input[-5]` to `input[-1]` might store sensitive data\nthat should not be given to `AddPacketInfo`, for example when callback functions\nare used as logging facility (through the API functions `wolfSSL_accept_ex` and\n`wolfSSL_connect_ex`).\n\nThis buffer over-read can be triggered at a server with a single Client Hello\nmessage. We have confirmed this with a proof-of-concept test case given below on\nwolfSSL 5.5.0, on the version from the master branch, and on version 5.4.0. A\nsimilar buffer over-read can be triggered at a client with the same wolfSSL\nversions.\n\n## DETAILS\n==========\n\n(Note: All code snippets and line numbers are with respect to the git hash\n`#43715d1bb5b8c5b8b18cba4be3171fd1dd7eb046` on remote\n`git@github.com:wolfssl/wolfssl.git`.)\n\nWhen executing the first proof of concept test case given below, we reach a call\nto `DoTls13HandShakeMsgType` from `tls13.c:DoTls13HandShakeMsg:10443` when the\nserver parses the Client Hello message, with the following values:\n\n```c\nsize = 16520;\ntotalSz = 16524;\n*inOutIdx = 4;\ntype = 1;\ninput; // buffer containing the input to be processed, before input,\nthere seems to be another input stored\n```\n\n`*inOutIdx=4` because of the call to `GetHandshakeHeader` at line\n`tls13.c:10411`.\n\nWe enter the function `tls13.c:DoTls13HandShakeMsgType` and because\n`WOLFSSL_CALLBACKS` flag is defined, we enter this snippet:\n\n```c\n#if defined(WOLFSSL_CALLBACKS)\n/* add name later, add on record and handshake header part back on */\nif (ssl->toInfoOn) {\nint add = RECORD_HEADER_SZ + HANDSHAKE_HEADER_SZ;\nAddPacketInfo(ssl, 0, handshake, input + *inOutIdx - add,\nsize + add, READ_PROTO, ssl->heap);\nAddLateRecordHeader(&ssl->curRL, &ssl->timeoutInfo);\n}", "creation_timestamp": "2026-09-02T01:01:26.646628Z"}, {"uuid": "4a227dad-a098-43f1-af4e-d1fa291aad30", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-42905", "type": "published-proof-of-concept", "source": "https://t.me/hacking_Attack/86320", "content": "Exploit Collector\nwolfSSL WOLFSSL_CALLBACKS Heap Buffer Over-Read\n\nhttps://3.bp.blogspot.com/-vLPaJ0bXchM/WWlvcii8AuI/AAAAAAAAIPY/lohzKYQrhRkUA5ocnA3xRTtIEj7YZIM-ACLcBGAs/s1600/h77.png \nwolfSSL versions prior to 5.5.2 suffer from a heap buffer over-read with WOLFSSL_CALLBACKS and can be triggered with a single Client Hello message.\n\nSHA-256 | 22c8bd75668677a45f903b9289dfd4de5cffd44e8f21af11820559278a985e59\n\nDownload\n# wolfSSL before 5.5.2: Heap-buffer over-read with WOLFSSL_CALLBACKS\n====================================================================\n\n## INFO\n=======\n\nThe CVE project has assigned the id CVE-2022-42905 to this issue.\n\nSeverity: 9.1 CRITICAL\nAffected version: before 5.5.2\nEnd of embargo: Ended October 28, 2022\nBlog Post: https://blog.trailofbits.com/2023/01/12/wolfssl-vulnerabilities-tlspuffin-fuzzing-ssh/\n\n## SUMMARY\n==========\n\nIf wolfSSL callback functions are enabled (i.e., the flag `WOLFSSL_CALLBACKS` is\nenabled), then a malicious client or network attacker can send a Client Hello\nmessage to a server that when parsed by the server will trigger a buffer\nover-read on the heap of at least 5 bytes. Similarly, a malicious server or a\nnetwork attacker can send a Hello Retry Request message to a client that when\nparsed by the client will trigger a buffer over-read on the heap of at least 15\nbytes.\n\nThe `AddPacketInfo` is given a buffer that should be the input buffer and that\nactually is shifted by 5 bytes on the left, i.e., instead of reading\n`input[0]..input[length]`, the function will read `input[-5]..input[length]` and\nstore it in a buffer that is exposed through the wolfSSL API. Note that `input`\nis stored on the heap and `input[-5]` to `input[-1]` might store sensitive data\nthat should not be given to `AddPacketInfo`, for example when callback functions\nare used as logging facility (through the API functions `wolfSSL_accept_ex` and\n`wolfSSL_connect_ex`).\n\nThis buffer over-read can be triggered at a server with a single Client Hello\nmessage. We have confirmed this with a proof-of-concept test case given below on\nwolfSSL 5.5.0, on the version from the master branch, and on version 5.4.0. A\nsimilar buffer over-read can be triggered at a client with the same wolfSSL\nversions.\n\n## DETAILS\n==========\n\n(Note: All code snippets and line numbers are with respect to the git hash\n`#43715d1bb5b8c5b8b18cba4be3171fd1dd7eb046` on remote\n`git@github.com:wolfssl/wolfssl.git`.)\n\nWhen executing the first proof of concept test case given below, we reach a call\nto `DoTls13HandShakeMsgType` from `tls13.c:DoTls13HandShakeMsg:10443` when the\nserver parses the Client Hello message, with the following values:\n\n```c\nsize = 16520;\ntotalSz = 16524;\n*inOutIdx = 4;\ntype = 1;\ninput; // buffer containing the input to be processed, before input,\nthere seems to be another input stored\n```\n\n`*inOutIdx=4` because of the call to `GetHandshakeHeader` at line\n`tls13.c:10411`.\n\nWe enter the function `tls13.c:DoTls13HandShakeMsgType` and because\n`WOLFSSL_CALLBACKS` flag is defined, we enter this snippet:\n\n```c\n#if defined(WOLFSSL_CALLBACKS)\n/* add name later, add on record and handshake header part back on */\nif (ssl->toInfoOn) {\nint add = RECORD_HEADER_SZ + HANDSHAKE_HEADER_SZ;\nAddPacketInfo(ssl, 0, handshake, input + *inOutIdx - add,\nsize + add, READ_PROTO, ssl->heap);\nAddLateRecordHeader(&ssl->curRL, &ssl->timeoutInfo);\n}", "creation_timestamp": "2026-09-04T23:00:04.056735Z"}, {"uuid": "b61e4292-1d1b-4e1e-a904-35c5931935de", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-42905", "type": "published-proof-of-concept", "source": "https://t.me/hacking_Attack/86320", "content": "Exploit Collector\nwolfSSL WOLFSSL_CALLBACKS Heap Buffer Over-Read\n\nhttps://3.bp.blogspot.com/-vLPaJ0bXchM/WWlvcii8AuI/AAAAAAAAIPY/lohzKYQrhRkUA5ocnA3xRTtIEj7YZIM-ACLcBGAs/s1600/h77.png \nwolfSSL versions prior to 5.5.2 suffer from a heap buffer over-read with WOLFSSL_CALLBACKS and can be triggered with a single Client Hello message.\n\nSHA-256 | 22c8bd75668677a45f903b9289dfd4de5cffd44e8f21af11820559278a985e59\n\nDownload\n# wolfSSL before 5.5.2: Heap-buffer over-read with WOLFSSL_CALLBACKS\n====================================================================\n\n## INFO\n=======\n\nThe CVE project has assigned the id CVE-2022-42905 to this issue.\n\nSeverity: 9.1 CRITICAL\nAffected version: before 5.5.2\nEnd of embargo: Ended October 28, 2022\nBlog Post: https://blog.trailofbits.com/2023/01/12/wolfssl-vulnerabilities-tlspuffin-fuzzing-ssh/\n\n## SUMMARY\n==========\n\nIf wolfSSL callback functions are enabled (i.e., the flag `WOLFSSL_CALLBACKS` is\nenabled), then a malicious client or network attacker can send a Client Hello\nmessage to a server that when parsed by the server will trigger a buffer\nover-read on the heap of at least 5 bytes. Similarly, a malicious server or a\nnetwork attacker can send a Hello Retry Request message to a client that when\nparsed by the client will trigger a buffer over-read on the heap of at least 15\nbytes.\n\nThe `AddPacketInfo` is given a buffer that should be the input buffer and that\nactually is shifted by 5 bytes on the left, i.e., instead of reading\n`input[0]..input[length]`, the function will read `input[-5]..input[length]` and\nstore it in a buffer that is exposed through the wolfSSL API. Note that `input`\nis stored on the heap and `input[-5]` to `input[-1]` might store sensitive data\nthat should not be given to `AddPacketInfo`, for example when callback functions\nare used as logging facility (through the API functions `wolfSSL_accept_ex` and\n`wolfSSL_connect_ex`).\n\nThis buffer over-read can be triggered at a server with a single Client Hello\nmessage. We have confirmed this with a proof-of-concept test case given below on\nwolfSSL 5.5.0, on the version from the master branch, and on version 5.4.0. A\nsimilar buffer over-read can be triggered at a client with the same wolfSSL\nversions.\n\n## DETAILS\n==========\n\n(Note: All code snippets and line numbers are with respect to the git hash\n`#43715d1bb5b8c5b8b18cba4be3171fd1dd7eb046` on remote\n`git@github.com:wolfssl/wolfssl.git`.)\n\nWhen executing the first proof of concept test case given below, we reach a call\nto `DoTls13HandShakeMsgType` from `tls13.c:DoTls13HandShakeMsg:10443` when the\nserver parses the Client Hello message, with the following values:\n\n```c\nsize = 16520;\ntotalSz = 16524;\n*inOutIdx = 4;\ntype = 1;\ninput; // buffer containing the input to be processed, before input,\nthere seems to be another input stored\n```\n\n`*inOutIdx=4` because of the call to `GetHandshakeHeader` at line\n`tls13.c:10411`.\n\nWe enter the function `tls13.c:DoTls13HandShakeMsgType` and because\n`WOLFSSL_CALLBACKS` flag is defined, we enter this snippet:\n\n```c\n#if defined(WOLFSSL_CALLBACKS)\n/* add name later, add on record and handshake header part back on */\nif (ssl->toInfoOn) {\nint add = RECORD_HEADER_SZ + HANDSHAKE_HEADER_SZ;\nAddPacketInfo(ssl, 0, handshake, input + *inOutIdx - add,\nsize + add, READ_PROTO, ssl->heap);\nAddLateRecordHeader(&ssl->curRL, &ssl->timeoutInfo);\n}", "creation_timestamp": "2026-09-05T01:00:09.037508Z"}]}