Recon
TRACE
method
TRACE
methodChecking for Cross-Site Tracing (XST) – Bypassing HttpOnly Cookies
If
TRACE
is enabled and the response reflects cookies, an attacker can bypass theHttpOnly
flag.Normally,
HttpOnly
prevents JavaScript from accessing cookies, butTRACE
can leak them if not properly restricted.
If the response includes the custom header,
TRACE
is enabled.If it leaks
Set-Cookie
headers, it’s a serious security issue.Bug Bounty Impact
: Session Hijacking
Finding Internal Headers & Debug Info
Some servers return sensitive internal headers when TRACE
is enabled, such as:
X-Forwarded-For
--> Real client IP leak.X-Backend-Server
--> Internal server exposure.Via
--> Reveals proxy setup.
Look for unusual headers in the response, which might reveal backend infrastructure details.
Bug Bounty Impact
:Information Disclosure
Finding WAF / Security Device Bypasses
Some
WAFs
don’t inspectTRACE
requests properly.You can use
TRACE
to test whetherWAF
protections apply to certain endpoints.
If
TRACE
reflects the payload, but normal requests are blocked, theWAF
is bypassable.
Checking for Cross-Origin Attacks
If
TRACE
is enabled, it might allowsame-origin policy (SOP)
bypasses.Some older browsers or misconfigured
CORS
setups can be exploited ifTRACE
echoes requests cross-origin.
Bypass User-Agent
filtering
User-Agent
filteringUse
HTTPBin
to check theUser-Agent
from any client.Experiment with those
User-Agent
:
Website Fingerprinting
SSL
Certificates
SSL
CertificatesUse
openssl
to get the certificate's info:
Create a custom wordlist with the subdomains to fuzz for response codes and gain a general idea of the content:
When working with
HTTPS
is good practice to validate theSSL/TLS
version and ciphers in use:
You can follow up with the
-cipher
flag to specify the cipher suites you're interested in:
Check if the server implements
HSTS
by looking for it's header:
Last updated