Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with infoleak
Search options answers only
not deleted
user 291964
This tag is for any class of exploits that leaks information relevant to further exploitation, such as stack cookies, kernel pointers, and memory layouts. It is not used for mere disclosure or loss of confidential data.
1
vote
Verbose Headers/Information Leakage via HttpResponse Headers vs fingerprinting via named hea...
The benefit of renaming such HTTP headers is very small in terms of security. As the OWASP correctly points out, an attacker can use all kinds of fingerprinting techniques and doesn't have to rely on …
- 23.5k