Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
cve-2015-3456 — Experiments related to CVE-2015-3456 | Kitploit
Tools/GitHubGitHub/vincentbernat/cve-2015-3456
Vulnerability AnalysisExploitationFuzzingPapers & ResearchLearning & EducationBinary Exploitation
GitHubvincentbernat/cve-2015-3456

cve-2015-3456

Experiments related to CVE-2015-3456

View Repository
1332811 years agoNot yet reviewed
Share

Experiments related to CVE-2015-3456

There is:

  • exploit/ is an "exploit" (it just crashes QEMU).
  • mock/ contains a stripped down version of QEMU. Only the vulnerability remains.
  • patch/ contains a program to patch a running instance of QEMU. The main point is to not need debug symbols, nor the original executable on disk. Therefore, some information have to be provided for this program to work as expected.

The main idea around all the live patching is to modify the command_to_handler array to make each command point to the "not implemented" function. While the process is partially stopped by ptrace (only the main thread), this seems a safe way to fix the vulnerability (as long as you don't care the floppy controller not working anymore).

This kind of patching works because command_to_handler is a static uninitialized variable and therefore ends up in the BSS segment which is writable. Also, except for PIE, the position of this segment in memory is known at compile time. Unfortunately, QEMU is usually compiled as PIE and therefore, that's not the case.

Of course, use at your own risk: modifying a running process could wreak havoc on the world!

More detailed information is available here: http://vincent.bernat.im/en/blog/2015-hotfix-qemu-venom.html

To better understand live patching, here are some links:

  • http://duartes.org/gustavo/blog/post/anatomy-of-a-program-in-memory/
  • https://lwn.net/Articles/631631/
  • http://www.openbsd.org/papers/nycbsdcon08-pie/index.html
  • https://www.technovelty.org/linux/plt-and-got-the-key-to-code-sharing-and-dynamic-libraries.html
  • http://phrack.org/issues/59/8.html
  • http://www.hick.org/code/skape/papers/needle.txt
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    755
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    510
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    415
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    343
  • 5

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    259
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    258

Explore all tools

Browse our collection of tools

View all tools →