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 123514
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
Security measures with JSONs watermarking and such
We can add new fields, we can and we might try but they're probably going to be the first ones that will be deleted by the attacker if a leak happens.
You assume the leaker would process the files.
…
- 6,284