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 51961
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.
6
votes
Will this Account Lockout mechanism increase the severity of a information leakage vulnerabi...
I would look at it the other way around:
Does knowing the list of users increase the severity of an attackable account lockout mechanism?
Usernames are generally not random but based on people's nam …
- 3,920