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-2025-2783 — This project is a research-oriented and educational simulation designed to demonstrate the concept of a sandbox escape vulnerability within Google Chrome (version 134.0.6998.177), leveraging improper handle , validation via Mojo IPC. | Kitploit
Tools/GitHubGitHub/bytereaper77/cve-2025-2783
Vulnerability AnalysisExploitationLearning & EducationBinary Exploitation
GitHubbytereaper77/cve-2025-2783

CVE-2025-2783

This project is a research-oriented and educational simulation designed to demonstrate the concept of a sandbox escape vulnerability within Google Chrome (version 134.0.6998.177), leveraging improper handle , validation via Mojo IPC.

View Repository
8381 year agoNot yet reviewed

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.

    972
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    666
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    424
  • 4

    jumpserver

    jumpserver/jumpserver

    JumpServer is an open-source Privileged Access Management (PAM) platform that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser.

    389
  • 5

    SafeLine

    chaitin/safeline

    Self-hosted WAF and reverse proxy that filters malicious HTTP traffic, blocks SQL injection, XSS, and bot attacks, with rate limiting and dynamic HTML/JS encryption.

    337
  • 6

    ARTEX

    baarai/artex

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

    331

Explore all tools

Browse our collection of tools

View all tools →
Share

SandBoxEscapeSim

CVE-2025-2783: Educational Sandbox Escape Simulation for Chrome

Author: Byte Reaper (@ByteReaper0)

Overview

This project is a research-oriented and educational simulation designed to demonstrate the concept of a sandbox escape vulnerability within Google Chrome (version 134.0.6998.177). It leverages improper handle validation via the Mojo IPC system to illustrate how a malicious actor might attempt to break out of the browser’s sandbox and access restricted resources.

Note: This is not a working exploit. All actions are simulated in a controlled environment for learning purposes only.

Features

  1. Mojo IPC Pipe Simulation Demonstrates the creation of a Mojo message pipe using Chrome’s IPC API.
  2. Fake Handle Injection Shows how to append a user-supplied, spoofed handle into an IPC message.
  3. Sandbox Permission Check Attempts to read various system paths to simulate a sandbox breakout.
  4. Readable Console Output Provides step-by-step feedback on the simulation status.

Prerequisites

  • A Windows environment (32‑bit or 64‑bit).
  • GCC or any compatible C compiler.
  • Mojo C headers (Chromium IPC library).
  • Windows SDK for WinAPI functions.
  • argparse.h for command-line parsing.

Compilation

gcc SandBoxEscapeSim.c argparse.c -o SandBoxEs -lmojo -lwindows

Adjust library flags as needed for your system.

Usage

./SandBoxEs -h <fake_handle>

Example:

./SandBoxEs -h 0xDEADBEEF

Simulation Flow

  1. System Check Validates the OS is Windows (32‑bit or 64‑bit).

  2. Retrieve Current User Uses WinAPI to get the logged-in username.

  3. Mojo Message Creation

    • Creates a message pipe.
    • Builds a message handle.
  4. Fake Handle Append

    • Injects the spoofed handle using MojoAppendMessageData().
    • Copies a sample payload ("Hello Browser") into the buffer.
  5. Message Write Sends the crafted message into the simulated browser pipe.

  6. Sandbox Escape Check Attempts to open and read files in protected locations:

    • C:\Windows\System32\config\SAM
    • C:\Windows\System32\config\SYSTEM
    • User Documents, Desktop, Downloads, and more.
  7. Result Report Outputs whether the simulated breakout succeeded.

Options

  • -h, --handle Specify a fake 32‑bit handle in hexadecimal (e.g., 0xDEADBEEF).

Output Interpretation

  • [+] Handle And Message Sent Successfully! The fake handle was accepted by the simulated pipe.
  • [+] SandBox Escape Success! The simulation was able to open a restricted file path, indicating an escape.
  • [-] Access Denied... Indicates the simulation could not read protected files.

Limitations & Disclaimer

  • Non-exploitative: All file reads and handle injections are purely simulated.
  • Educational Use Only: Do not run against real browsers or production environments.
  • Controlled Environment: Always test in an isolated VM or lab setup.

Warnings & Safety

Running this code outside of a sandboxed VM may lead to undefined behavior. Unauthorized testing on production machines or networks is strictly forbidden.

Dependencies

  • mojo/public/c/system/functions.h
  • mojo/public/c/system/types.h
  • mojo/public/c/system/message_pipe.h
  • windows.h, lmcons.h
  • argparse.h

License

This project is released under the MIT License.

Contact

  • Author: Byte Reaper
  • Telegram: @ByteReaper0

Happy Learning!

Download Tool