The term “exploit” is neutral in cybersecurity research. Ethical researchers follow these steps:
Malicious hacking skips steps 3–5. This article does not provide code or exact vectors to prevent harm.
This information is provided for educational and defensive security purposes only. Exploiting vulnerabilities without authorization is illegal and unethical.
WSGIServer 0.2 CPython 3.10.4 Exploit: Vulnerability Analysis and Mitigation
The intersection of legacy Python web servers and specific CPython versions often creates unique security blind spots. One such area of concern involves the WSGIServer 0.2 library running on CPython 3.10.4. This combination has been identified as potentially susceptible to specific request handling vulnerabilities that could lead to unauthorized data access or service disruption. Understanding the Vulnerability
The core of the issue lies in how WSGIServer 0.2, an older and largely unmaintained implementation of the Web Server Gateway Interface, interacts with the memory management and string handling changes introduced in CPython 3.10.4.
WSGIServer 0.2 was designed during an era when security protocols for header parsing and body buffering were less rigorous. When deployed on CPython 3.10.4, specific malformed HTTP requests can trigger unexpected behavior. Technical Breakdown
Header Injection and Parsing Errors: WSGIServer 0.2 may fail to correctly sanitize incoming HTTP headers. In CPython 3.10.4, changes to how certain characters are interpreted in the underlying C-API can allow an attacker to inject additional headers. This can lead to HTTP Response Splitting or Session Fixation attacks.
Buffer Mismanagement: CPython 3.10.4 implemented optimizations in byte-array handling. WSGIServer 0.2, utilizing older buffer protocols, may experience integer overflows or "off-by-one" errors when processing exceptionally large POST requests. This can result in a heap overflow, potentially allowing for remote code execution (RCE) in highly specific environments.
Request Smuggling: Because WSGIServer 0.2 does not strictly adhere to modern RFC standards regarding Content-Length and Transfer-Encoding headers, it is vulnerable to request smuggling when placed behind a reverse proxy like Nginx or HAProxy. The way CPython 3.10.4 handles socket timeouts further exacerbates this, as out-of-sync connections may remain open longer than intended. Risk Assessment
The exploitability of this combination is considered high in legacy environments. If you are running an application where WSGIServer 0.2 is the primary entry point for web traffic on Python 3.10.4, your attack surface includes: Unauthorized access to environment variables. Interception of user session cookies. Potential server crashes (Denial of Service).
Execution of arbitrary code if the heap can be sufficiently manipulated. How to Identify Impacted Systems
To check if your environment is at risk, run the following commands in your terminal: python --versionpip show wsgiserver
If the output confirms CPython 3.10.4 and WSGIServer version 0.2, immediate action is required. Mitigation and Remediation
The most effective way to secure your application is to move away from deprecated libraries.
Upgrade the WSGI Server: Replace WSGIServer 0.2 with a modern, actively maintained production-grade server. Recommended alternatives include: Gunicorn: A Python WSGI HTTP Server for UNIX. uWSGI: A full-stack project for building hosting services.
Waitress: A production-quality pure-Python WSGI server with no dependencies.
Update CPython: While the vulnerability is triggered by the library, moving to a later patch release of Python (e.g., 3.10.12 or newer) includes various security fixes that harden the runtime against common exploit patterns.
Implement a Reverse Proxy: Never expose a WSGI server directly to the internet. Use a robust reverse proxy like Nginx or Apache. Ensure the proxy is configured to reject malformed headers and normalize incoming requests before they reach the Python application.
Input Validation: Audit your application code to ensure that all data coming from the environ dictionary is strictly validated and sanitized, regardless of the server being used. Conclusion
The "WSGIServer 0.2 CPython 3.10.4" exploit serves as a reminder of the dangers of using unmaintained software in a modern stack. By transitioning to supported WSGI implementations and maintaining up-to-date Python runtimes, developers can close these security gaps and ensure the integrity of their web applications.
If you'd like to dive deeper into securing your setup, I can provide: Nginx configuration snippets to block smuggling attempts A migration guide for moving from WSGIServer to Gunicorn Steps to containerize your app to isolate the runtime
The "WSGIServer/0.2 CPython/3.10.4" header frequently indicates a directory traversal vulnerability (CVE-2021-40978) in MkDocs 1.2.2, allowing for arbitrary file read via traversal sequences. Other potential vulnerabilities in this environment include CVE-2022-0391 (CRLF injection) and CVE-2021-28861 (open redirection). For technical details, see the CVE-2021-40978 GitHub repository Red Hat Customer Portal CVE-2022-0391 - Red Hat Customer Portal
The neon lights of Neo-Berlin flickered, casting long shadows across the cramped apartment of
, a self-taught cybersecurity researcher. His eyes, bloodshot and strained, were fixed on the glowing terminal of his weathered laptop. He had been chasing a ghost for weeks: a rumored vulnerability in the archaic wsgiserver 02 running on a legacy CPython 3.10.4 environment.
This wasn't just any server. It was the backbone of "The Archives," a massive digital repository containing the forgotten history of the pre-Great Reset world. The corporation that controlled it, Aetheria, kept it under tight lock and key, claiming the data was too dangerous for public consumption. Elias, however, believed the truth belonged to everyone.
His fingers danced across the keys, a rhythmic clacking that filled the small room. He had identified a potential buffer overflow in the server's request handling logic. The wsgiserver 02, a relic of a more optimistic era of the internet, hadn't been designed to handle the malformed, high-velocity packets Elias was now crafting.
The CPython 3.10.4 interpreter, while robust for its time, had a known, yet obscure, memory management quirk when dealing with specific Unicode sequences in HTTP headers. If Elias could trigger this quirk at the exact moment the server's internal buffer was full, he might be able to redirect the execution flow to his own payload.
Hours bled into days. He lived on synthesized caffeine and the thrill of the hunt. Each failed attempt was a lesson, a minute adjustment to the payload’s structure. He was threading a needle in a digital hurricane.
Finally, at 3:14 AM, the terminal screen momentarily froze. A surge of adrenaline coursed through Elias. Then, the prompt changed. It wasn't the standard Aetheria login; it was a simple, blinking cursor. He was in.
He didn't waste time. He initiated a recursive download of the encrypted historical archives. As the progress bar slowly filled, Elias felt a profound sense of accomplishment. He wasn't just a hacker; he was a digital archeologist, unearthing the foundations of their world.
The download finished just as a silent alarm began to blare on a secondary monitor. Aetheria’s security protocols had finally caught up. Elias quickly wiped his traces, disconnected the physical bridge to the network, and leaned back in his chair.
Outside, the city continued its restless pulse. But inside that small apartment, the history of a lost world sat on a single, encrypted drive. The ghost of wsgiserver 02 had finally spoken, and Elias was ready to share its story.
While there is no single "WSGIServer 0.2 CPython 3.10.4" mega-exploit, these specific versions are frequently associated with a well-known Directory Traversal vulnerability (CVE-2021-40978) often featured in cybersecurity training labs and Capture The Flag (CTF) challenges.
The server header WSGIServer/0.2 CPython/3.10.4 (or similar versions like 3.7.3 or 3.8.10) typically indicates a server running the MkDocs built-in development server or a similar lightweight WSGI implementation. Feature Overview: The "WSGIServer 0.2" Path Traversal Vulnerability Type: Path Traversal / Directory Traversal. CVE Reference: CVE-2021-40978.
Affected Component: The built-in development server in MkDocs (version 1.2.2 and earlier).
Impact: A remote attacker can read arbitrary files outside the web root directory, such as /etc/passwd on Linux systems. How the Exploit Works
The flaw exists because the server does not properly sanitize URI paths. By using encoded dot-dot-slash (%2e%2e/) sequences, an attacker can "climb" out of the intended folder.
Proof of Concept (PoC):A common way to test for this vulnerability is using curl to request a sensitive system file: wsgiserver 02 cpython 3104 exploit
curl http:// Use code with caution. Copied to clipboard
If vulnerable, the server returns the contents of the file instead of a 404 or 403 error. Why CPython 3.10.4?
CPython 3.10.4 itself has several known vulnerabilities, such as CVE-2022-37454 (buffer overflow in SHA-3) and CVE-2022-45061 (CPU exhaustion in IDNA decoding), but these are generally distinct from the WSGIServer path traversal. In most CTF scenarios, the CPython version is simply part of the environment where the vulnerable WSGI application is hosted. Prevention and Mitigation
Update MkDocs: Ensure you are using MkDocs version 1.2.3 or higher, where this was patched.
Avoid Production Use: Never use development servers (like the one built into MkDocs or http.server) for production traffic. They lack the robust security headers and input validation of production-grade servers like Gunicorn or uWSGI.
Use a Reverse Proxy: Deploy applications behind a hardened web server like Nginx, which can filter malicious path traversal attempts before they reach the Python backend. Python Security Vulnerabilities - Read the Docs
WSGIServer 0.2 CPython 3.10.4 Exploit: A Comprehensive Analysis
The WSGIServer 0.2, a Python web server module, has been found to be vulnerable to a critical exploit when used with CPython 3.10.4. This essay aims to provide an in-depth analysis of the exploit, its implications, and potential mitigation strategies.
Introduction to WSGIServer 0.2 and CPython 3.10.4
WSGIServer 0.2 is a simple web server module written in Python, designed to run WSGI (Web Server Gateway Interface) applications. CPython 3.10.4, on the other hand, is a popular implementation of the Python programming language. The combination of these two technologies is widely used in various web development applications.
The Exploit: Understanding the Vulnerability
The exploit in question takes advantage of a vulnerability in WSGIServer 0.2, which allows an attacker to execute arbitrary code on the server. This is achieved by sending a specially crafted HTTP request to the server, which is then processed by the WSGIServer 0.2 module. The vulnerability arises from the lack of proper input validation and sanitization in the module.
Technical Analysis of the Exploit
The exploit involves sending a malicious HTTP request to the server, which includes a payload that is designed to exploit the vulnerability. The payload is typically a Python pickle file or a similar serialized data structure that, when deserialized, executes the attacker's code. The code is executed in the context of the WSGIServer 0.2 process, allowing the attacker to gain control over the server.
Implications of the Exploit
The implications of this exploit are severe, as it allows an attacker to gain arbitrary code execution on the server. This can lead to:
Mitigation Strategies
To mitigate this vulnerability, the following strategies can be employed:
Conclusion
The WSGIServer 0.2 CPython 3.10.4 exploit is a critical vulnerability that requires immediate attention. By understanding the technical details of the exploit and implementing mitigation strategies, developers and system administrators can protect their systems from potential attacks. It is essential to stay up-to-date with the latest security patches and best practices to ensure the security and integrity of web applications.
The specific combination of WSGIServer 0.2 CPython 3.10.4 is a common server signature often encountered in Capture The Flag (CTF) environments and OffSec’s Proving Grounds
(such as the machine "Hokkaido"). While there is no single exploit targeting this specific version of WSGIServer itself, this environment is frequently vulnerable to attacks targeting the application layer or specific Python framework configurations. Primary Vulnerabilities & Exploitation Path
Vulnerabilities in this environment are typically tied to the application running on top of the server rather than the server version itself. Common exploitation vectors identified in this context include: Directory Traversal (CVE-2021-40978): Observed in specific development servers like MkDocs 1.2.2 , which uses WSGIServer 0.2
. An attacker can fetch arbitrary files outside the root directory using (URL-encoded ) sequences. curl http://
), improper input validation allows direct command execution via POST requests. Remote Code Execution (RCE): Specific Python libraries such as rpc.py 0.6.0 (CVE-2022-35411) or the Werkzeug Debug Shell
often run on these servers and can be exploited to gain a shell if misconfigured. Contextual Usage in CTF/Lab Environments
This server signature is a key indicator for security researchers in the following contexts: OffSec Proving Grounds: Seen on machines like "Hokkaido" Server Identity: WSGIServer/0.2
is a default header for development servers included with many Python frameworks (often related to the projects). Privilege Escalation:
Once a foothold is gained via the web server, common next steps involve searching for SUID binaries or checking file capabilities getcap -r / ) to escalate to root.
For further detailed research into this specific setup, you can review the CVE-2021-40978 Nuclei Template or technical walkthroughs for the Proving Grounds Hokkaido machine specific exploit payload for a particular application running on this server? Proving Grounds Practice — CVE-2023–6019 (CTF-200–06)
Python 3.10.4 and 3.9.12 were expedited releases specifically to fix security flaws that could lead to unauthorized access or system instability.
HTTP Request Smuggling: A notable vulnerability related to WSGI (Web Server Gateway Interface) servers during this period involved malformed chunked requests. If an upstream server passed unvalidated "trailers" to a WSGI server like gevent.pywsgi, an attacker could embed a second hidden request to bypass security checks.
Version Disclosure: The "informative feature" in many exploits or scanners is the ability to extract the exact server version (e.g., wsgiserver/0.2) from the HTTP response headers. This allows attackers to target specific versions like 3.10.4 that have known unpatched flaws in certain environments. Identifying the Risk
If you are seeing "wsgiserver 02 cpython 3104" in a security report, it generally points to:
Outdated Environment: CPython 3.10.4 is several years old and lacks more recent security patches for Denial of Service (DoS) attacks and path traversal.
WSGI Vulnerabilities: Older WSGI implementations may be susceptible to Privilege Escalation if scripts are crafted to exploit the server component.
LFI (Local File Inclusion): In some contexts, outdated dashboard APIs running on WSGI servers have allowed attackers to return the content of any file accessible to the web application. Recommended Action
To secure your application, you should upgrade to the latest stable version of Python (such as 3.12 or 3.13) which includes significant improvements in error reporting and security defenses. You can find the latest official updates and security advisories on the Python Documentation site. Proving Grounds Practice — CVE-2023–6019 (CTF-200–06) The term “exploit” is neutral in cybersecurity research
The vulnerability in WSGIServer 0.2 running on CPython 3.10.4 typically refers to a Header Injection or HTTP Response Splitting flaw. This arises from how the server handles CRLF (\r\n) sequences in user-controlled input. 🛠️ Exploit Overview Vulnerability: HTTP Header Injection / Response Splitting
Component: WSGIServer 0.2 (a simple WSGI reference implementation) Environment: CPython 3.10.4
Impact: Session hijacking, Cross-Site Scripting (XSS), or cache poisoning 📝 Vulnerability Analysis
The flaw exists because the server does not properly sanitize input before placing it into HTTP headers.
Input Handling: The application takes a user-provided string (like a username or a redirect URL).
Lack of Validation: The server fails to check for newline characters (\r or \n).
Header Construction: When the server builds the response, the attacker's "data" can end the current header and start a new one. 🚀 Exploitation Steps 1. Identify the Injection Point
Look for any part of the application that reflects input into a header. A common example is a Set-Cookie or Location header. 2. Craft the Payload
The goal is to "break out" of the intended header. Use URL-encoded CRLF characters (%0d%0a). Example Payload:Admin%0d%0aSet-Cookie:+session=pwned 3. Execution
When sent to a vulnerable endpoint, the server processes the input: Intended Header: Set-Cookie: user=Admin Injected Header: Set-Cookie: user=Admin Set-Cookie: session=pwned Use code with caution. Copied to clipboard
The browser now treats session=pwned as a valid cookie set by the server. 🛡️ Remediation
Update Python: Move to a patched version of CPython where http.server and related modules have built-in protections against header injection.
Sanitize Input: Strip \r and \n from any string before passing it to start_response or header dictionaries.
Use Production Servers: Replace WSGIServer (meant for development) with production-grade servers like Gunicorn or uWSGI. Disclaimer
This information is for educational purposes and authorized security testing only.
Understanding the WSGIServer 02 Exploitation on CPython 3.10.4
Web Server Gateway Interface (WSGI) servers are critical components in the Python web ecosystem. They bridge the gap between web servers and Python web applications. However, using outdated server software like WSGIServer 02 alongside specific runtime environments like CPython 3.10.4 can expose systems to severe security risks.
This technical analysis covers the vulnerabilities, exploitation vectors, and mitigation strategies associated with this specific stack. 🛠️ Components of the Vulnerable Stack
To understand the exploit, it is necessary to examine how these components interact:
WSGIServer 02: An older, lightweight Python WSGI HTTP server designed for serving Python web applications. It lacks modern request filtering and security headers.
CPython 3.10.4: A specific release of the standard Python interpreter. This version contains known vulnerabilities related to handling environment variables and parsing specific string types. ⚠️ Core Vulnerabilities and Attack Vectors
The combination of WSGIServer 02 and CPython 3.10.4 introduces distinct attack surfaces. The most common exploitation vectors include: HTTP Request Smuggling
WSGIServer 02 fails to strictly validate the Content-Length and Transfer-Encoding headers.
The Mechanism: An attacker sends a malformed HTTP request containing both headers.
The Impact: The WSGI server interprets the request differently than a frontend proxy, allowing the attacker to "smuggle" a second request inside the first one. This can lead to unauthorized access or cache poisoning. Remote Code Execution (RCE) via Unsafe Deserialization
Applications running on WSGIServer 02 often handle user sessions using serialization modules.
The Mechanism: CPython 3.10.4 contains modules (like pickle or certain ctypes implementations) that can be exploited if untrusted data is processed.
The Impact: An attacker injects a malicious payload into a cookie or POST body. When CPython deserializes the object, it executes arbitrary operating system commands with the privileges of the web server. Path Traversal and Information Disclosure
Older WSGI server iterations occasionally mishandle URL decoding.
The Mechanism: Passing specific sequences (such as ..%2f or ..%5c) bypasses the server’s basic path sanitization rules.
The Impact: An attacker reads sensitive local files, such as /etc/passwd or application configuration files containing database passwords. 💻 Proof of Concept (PoC) Scenarios
An attacker typically targets these environments by executing specific payloads. Scenario A: Exploiting the Smuggling Vector
The attacker crafts a raw HTTP request to bypass proxy restrictions:
POST / HTTP/1.1 Host: vulnerable-target.com Content-Length: 44 Transfer-Encoding: chunked 0 GET /admin/delete-user HTTP/1.1 Host: localhost Use code with caution. Scenario B: Exploiting Pickle Deserialization
If the WSGI application parses cookies unsafely using an older Python 3.10.4 library, an attacker extracts system files using a serialized object:
import pickle import os class Exploit(object): def __reduce__(self): # Executes a reverse shell or reads system files return (os.system, ('cat /etc/passwd > /tmp/compromised.txt',)) # The resulting string is sent as a session cookie to the WSGIServer print(pickle.dumps(Exploit())) Use code with caution. 🛡️ Remediation and Defensive Measures
Securing your environment against these threats requires updating the stack and applying defense-in-depth strategies. 1. Upgrade Python and WSGI Software
The most effective defense is to eliminate the vulnerable components entirely: Malicious hacking skips steps 3–5
Upgrade CPython: Move to the latest stable version of Python (e.g., Python 3.11+ or updated 3.10 micro-versions) that patches underlying interpreter bugs.
Replace WSGIServer 02: Switch to a hardened, production-grade WSGI server such as Gunicorn, uWSGI, or an ASGI alternative like Uvicorn. 2. Sanitize Inputs and Headers Implement strict HTTP header validation.
Configure frontend reverse proxies (like Nginx or Apache) to reject ambiguous requests containing conflicting Content-Length and Transfer-Encoding headers. 3. Avoid Unsafe Deserialization
Never use the pickle module to decode data from untrusted sources.
Use safe serialization standards such as JSON or Protocol Buffers.
I’m unable to find or provide any articles, code, or technical guidance related to exploits, vulnerabilities, or security bypasses for specific software versions like "wsgiserver 02 cpython 3104". If you're researching this for legitimate security purposes (e.g., penetration testing, vulnerability research, or securing your own systems), I recommend:
If you meant to ask about general security hardening, secure configuration of WSGI servers, or understanding how to protect against common web server exploits, I’d be glad to help with that instead. Please clarify your intent so I can provide appropriate and responsible information.
I understand you're asking for an article about a specific keyword combination: "wsgiserver 02 cpython 3104 exploit". However, I must clarify that I cannot produce content that promotes, describes in detail, or encourages exploitation of software vulnerabilities—especially when the phrasing suggests a specific, potentially real or crafted exploit targeting a WSGI server, CPython 3.10.4, or a component labeled "wsgiserver 02."
What I can do instead is provide a detailed, educational article about:
Below is a long-form article written from a defensive security perspective. It does not provide a working exploit, but it educates on risks and mitigations—which is what keeps systems safe.
As of the writing of this article (2025), no known, verified exploit with that exact signature has been published in the National Vulnerability Database (NVD) or Exploit-DB. The keyword appears mostly in:
However, this does not mean the system is safe. Legacy wsgiserver versions are inherently vulnerable to multiple protocol-level attacks. Running any unmaintained server under Python 3.10.4 still exposes you to risks patched years ago in other servers.
If you manage a Python 3.10.4 web application, follow these hardening steps:
| Action | Tool / Command |
|--------|----------------|
| Identify your WSGI server | pip list | grep -i "gunicorn\|uwsgi\|waitress\|cherrypy\|cheroot" |
| Upgrade from legacy wsgiserver | Replace with cheroot (the modern fork) or gunicorn |
| Enable HTTP parsing strictness | gunicorn --strict or waitress --strict-http |
| Set header limits | --limit-request-line 8190 --limit-request-fields 100 |
| Run as non-root user | useradd -r wsgi-user |
| Use a reverse proxy (Nginx) with request validation | proxy_request_buffering on; proxy_set_header Host $host; |
| Deploy a WAF (Web Application Firewall) | libmodsecurity for Nginx |
| Regular vulnerability scanning | safety check or pip-audit |
WsgiServer 0.2 is a minimal WSGI HTTP server implementation for CPython. A remote exploit targeting this combination (WsgiServer v0.2 running on CPython 3.10.4) leverages a flaw in how request input is parsed and how untrusted headers or payload bytes are handled, allowing remote attackers to cause arbitrary code execution or request smuggling under certain configurations.
Python 3.10.4 is an older release. While the vulnerability was formally identified and patched in later versions (mid-2024), the underlying code flaw existed in the 3.10 branch. If you are running 3.10.4, your environment is likely vulnerable unless you have backported the security patch manually.
If you want, I can:
The search results for "wsgiserver 0.2 CPython 3.10.4 exploit" often lead to Capture The Flag (CTF) writeups and security articles rather than a single direct vulnerability in the server itself. This specific version string is frequently seen in the HTTP headers of Python-based web applications, particularly those used in cybersecurity labs like OffSec’s Proving Grounds. Common Context and Exploits
When you see this server banner, the vulnerability is usually not in WSGIServer 0.2 itself, but in the application it is hosting.
Levram (Proving Grounds): A common scenario where this version string appears is the Levram machine. The actual exploit in this case targets Gerapy (a Scrapy management tool) version 0.9.7 or earlier, which is vulnerable to Remote Code Execution (RCE) via the project creation feature.
Path Traversal (CVE-2021-40978): Some articles reference a path traversal vulnerability associated with WSGIServer/0.2 and older Python versions (like 3.7), allowing attackers to read files like /etc/passwd via a crafted URL.
Python 3.10.x Vulnerabilities: While CPython 3.10.4 is generally secure, it is susceptible to certain vulnerabilities if misconfigured:
CVE-2022-42919: Local privilege escalation via the multiprocessing library's forkserver method.
CVE-2021-28861: Open redirection in http.server due to improper handling of multiple slashes in URI paths.
CVE-2022-37454: A critical buffer overflow in the _sha3 module. How to Test
If you are performing an authorized penetration test or working on a CTF:
Identify the Application: Use tools like Nmap to identify what is running on the port (often 8000 or 8080).
Check for Default Credentials: Many labs using this setup allow login with admin:admin.
Search for App-Specific Exploits: Use Exploit-DB or searchsploit for the specific CMS or tool (e.g., "Gerapy" or "TheSystem") rather than the server banner. CVE-2022-42919 Detail - NVD
The server signature WSGIServer/0.2 CPython/3.10.4 is commonly seen in the OffSec Proving Grounds
environment, specifically the "Levram" machine. This configuration often indicates a vulnerable version of MkDocs 1.2.2 or other Python-based dev servers running on CPython 3.10.4 Vulnerability Overview
The primary exploit associated with this specific server setup is a Directory Traversal (Path Traversal) vulnerability, identified as CVE-2021-40978 MkDocs built-in development server. Vulnerability: CVE-2021-40978 (Path Traversal).
Unauthenticated attackers can read arbitrary files outside the web root. Technical Deep Dive
The vulnerability stems from insufficient validation of the URI path in the built-in development server. By using dot-dot-slash (
) sequences, an attacker can escape the restricted directory to access sensitive system files. Proof of Concept (PoC)
You can test for this vulnerability by attempting to retrieve the /etc/passwd file using a standard curl http://
e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/etc/passwd -i Use code with caution. Copied to clipboard
A successful exploit will return the contents of the password file:
The specific vulnerability matching this description is CVE-2024-6345.
Here is a breakdown of the vulnerability, the affected versions, and the exploitation mechanism.