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-32463 — Provides a containerized environment and signed Nuclei template to safely test CVE-2025-32463, a sudo privilege escalation vulnerability, with detection and patched version comparison. | Kitploit
Tools/GitHubGitHub/ricardomaia/cve-2025-32463
Vulnerability ScannersContainer SecurityExploitationPenetration TestingLearning & EducationLabs & Practice
GitHubricardomaia/cve-2025-32463

CVE-2025-32463

Provides a containerized environment and signed Nuclei template to safely test CVE-2025-32463, a sudo privilege escalation vulnerability, with detection and patched version comparison.

View Repository
431 year agoNot yet reviewed
Share

CVE-2025-32463 - Setup and Execution Guide

This is the first time I’ve ported a malicious exploit into a Nuclei template for a non-intrusive vulnerability scan that still demonstrates the underlying issue.

I documented the process in more detail expressly as a learning exercise.

My main challenges were:

  • How to modify the original exploit code into something safe that can effectively test privilege escalation without obtaining a root shell as the original exploit did.
  • I ran into some issues with Nuclei template syntax when using the code engine. I’m not accustomed to creating templates this way, so I was caught a few times by the need to sign the template and include the -itags local parameter, since the local tag is ignored by default in .nuclei-ignore settings.
  • I was unsure whether compiling C code inside a template is an accepted approach (there are very few examples like that in the official repository).

It may seem weird that I chose the Windows environment for this activity. The fact is that Windows is my default operating system for reasons I won’t go into here.

Containerized Environment Setup

docker-compose up --build -d

Signing the Nuclei Template (Required for Code Engine)

This template uses code engine which requires signing for security reasons. The template is already signed in this repository.

Signing keys setup (already configured)

The docker-compose.yaml is configured to mount your Windows Nuclei signing keys from %APPDATA%\nuclei\keys into the containers. This allows the signed template to be verified.

If you need to re-sign the template on your host:

On Windows host (requires Nuclei installed).

nuclei -t cve-2025-32463.yaml -sign

This will sign the template and add a digest field.

Note: The first time you run this command, Nuclei will create signing keys in %APPDATA%\nuclei\keys and prompt for:

  1. User/Organization Name
  2. Passphrase for the private key

Execute Nuclei scan inside the target container

Vulnerable Sudo Version

Linux/macOS/Git Bash:

docker exec -u testuser vulnerable-sudo-target sh -c 'nuclei -itags local -t /tmp/template.yaml -target localhost -code'

Windows PowerShell/CMD:

docker exec -u testuser vulnerable-sudo-target sh -c "nuclei -itags local -t /tmp/template.yaml -target localhost -code"

Alternative (works on all platforms):

docker exec -u testuser vulnerable-sudo-target nuclei -itags local -t /tmp/template.yaml -target localhost -code

Notes:

  • The -code flag is required to enable code protocol-based templates
  • Use sh -c '...' to avoid Windows path conversion issues with MSYS2/Git Bash
  • The template should show: [INF] Executing 1 signed templates from <your-username>

Patched Sudo Version

Windows PowerShell/CMD:

docker exec -u testuser patched-sudo-target sh -c "nuclei -itags local -t /tmp/template.yaml -target localhost -code"

Alternative (works on all platforms):

docker exec -u testuser patched-sudo-target nuclei -itags local -t /tmp/template.yaml -target localhost -code

Notes:

  • The -code flag is required to enable code protocol-based templates
  • Windows Git Bash: Use double quotes "..." or the alternative command without sh -c
  • The template should show: [INF] Executing 1 signed templates from <your-username>

Alternative: Manual Exploit Test

If you want to verify the vulnerability without signing the Nuclei template, you can run the exploit script directly:

Copy and run the exploit script.

docker cp exploit.sh vulnerable-sudo-target:/tmp/exploit.sh
docker exec -u testuser vulnerable-sudo-target bash /tmp/exploit.sh

Expected output: woot! followed by a root shell (in interactive mode).

Expected Output

Nuclei Scan Output - Vulnerable Container

[CVE-2025-32463] [code] [critical] localhost ["VULNERABLE UID=1000 EUID=0"]

[INF] Executing 1 signed templates from <your-username>
[INF] Scan completed in 140.454595ms. 1 matches found.

Detection confirmed: UID=1000 EUID=0 proves that code from testuser (1000) executed with root privileges (0).

Nuclei Scan Output - Patched Container

[INF] Executing 1 signed templates from <your-username>
[INF] Scan completed in 143.319373ms. No results found.

No vulnerability detected - The patched sudo version prevents the library loading.

See Also

For detailed technical explanation of the vulnerability, attack vectors, and detection methodology, refer to the Technical Notes document.

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.

    591
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    481
  • 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.

    389
  • 4

    redforge

    cybersecurity91/redforge

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

    332
  • 5

    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.

    255
  • 6

    antifox

    antifox-ai/antifox

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

    247

Explore all tools

Browse our collection of tools

View all tools →