{"uuid": "924ad15b-90ed-47db-8c6c-46a5ff1ecd3a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-1262", "type": "published-proof-of-concept", "source": "https://t.me/ptswarm/166", "content": "Debugging D-Link: Emulating firmware and hacking hardware\n\n\ud83d\udc64 by Matthew Remacle\n\nThis blog aims to explain the process of gaining a foothold in firmware or a physical device for vulnerability research and achieving a debuggable interface. While existing Proof-Of-Concept code for (yet another) D-Link vulnerability CVE-2022-1262 is utilized within this document, as well as strong hints at suspect areas of code, don\u2019t expect to find any new ready-to-fire exploits buried in the contents below.\n\n\ud83d\udcdd Contents:\n\u25cf What Vulnerability?\n\u25cf How to trigger the vulnerability?\n\u25cf Obtain copies of prog.cgi\n\u25cf Patch Diffing\n\u25cf Uses of strcat()\n\u25cf Debugging with Emulation\n\u25cf Debugging With Physical Device\n\u25cf Conclusion\n\nhttps://www.greynoise.io/blog/debugging-d-link-emulating-firmware-and-hacking-hardware", "creation_timestamp": "2023-03-17T06:35:30.000000Z"}