31,492 reputation
343114
bio website bishopfox.com
location
age
visits member for 4 years, 2 months
seen 8 hours ago

Test everything, trust no one.

Do not trust any security related answers you see on StackOverflow.com (SO) / Security.StackExchange.com (SE). Not from me, not from anyone. There are very smart people on SO/SE and there are excellent answers given, although the right answer is not always chosen.

I have been writing exploit code for a while. There is no perfect system, vulnerable code will always exist.


Dec
28
revised Now that it is 2015, what SSL/TLS cipher suites should be used in a high security HTTPS environment?
edited body
Dec
28
asked Now that it is 2015, what SSL/TLS cipher suites should be used in a high security HTTPS environment?
Dec
26
comment Could a compromised WP database cause re-infection without the hacker needing to login into WP?
@lankip Honey Badger don't care about changing passwords.
Dec
26
revised Could a compromised WP database cause re-infection without the hacker needing to login into WP?
added 92 characters in body
Dec
26
revised Could a compromised WP database cause re-infection without the hacker needing to login into WP?
added 92 characters in body
Dec
26
comment Could a compromised WP database cause re-infection without the hacker needing to login into WP?
@blankip you maybe surprised. The OP didn't describe their infection, but there are bots that just compromise WP databases to post spam, and gain a kind of persistent-xss to deliver drive-by exploits.
Dec
26
comment MS03-026 RPC DCOM Exploit not working on metasploit
There is not enough information to answer this question. You maybe using a decade old exploit, maybe you are patched? Which one of the dozen or so dcom exploits are you attempting to use?
Dec
26
comment Could a compromised WP database cause re-infection without the hacker needing to login into WP?
This is shellcode: exploit-db.com/shellcode . It is always a binary payload, usually written in Assembler, although it could also be written in C, and then turned into a binary payload, it can never be written in an interpreted language.
Dec
26
revised Could a compromised WP database cause re-infection without the hacker needing to login into WP?
added 7 characters in body
Dec
26
comment Could a compromised WP database cause re-infection without the hacker needing to login into WP?
shellcode is the payload for a memory corruption vulnerability, we are talking about a PHP application here. A backdoor that gives you a shell is not shellcode.
Dec
26
comment Could a compromised WP database cause re-infection without the hacker needing to login into WP?
"php shellcode"? I don't think you are using the word shellcode properly.
Dec
26
answered Could a compromised WP database cause re-infection without the hacker needing to login into WP?
Dec
26
comment How I do get the correct the Tamper parameters from an internal web login
TamperData is crap, use BURP or ZAP.
Dec
25
comment is HttpOnly and Secure cookie enough to prevent CSRF in rest api?
What you just described in your comment is a 'double submit cookie' and referenced by the OWASP CSRF prevention cheat sheet. What you described in your post is a vulnerability. A cookie alone cannot prevent CSRF.
Dec
25
awarded  web-application
Dec
23
comment Is SQL injection possible with LIMIT?
Sorry but, this is a huge pet peeve of mine. Mainly because I really wish query stacking was supported by majority of SQL databases, but in the real world it is very uncommon (MS-SQL, Access, SQLite). I see posts talking about query stacking as providing false hope.
Dec
23
comment Is SQL injection possible with LIMIT?
Query stacking? In MySQL? Have you ever exploited SQL Injection on MySQL??? PiTheNumber got he right answer.
Dec
23
comment is HttpOnly and Secure cookie enough to prevent CSRF in rest api?
A cookie can't prevent CSRF, the point of CSRF is that you are riding on a session because all requests to a domain contain a cookie. Perhaps you are confused by how double-submit CSRF tokens work?
Dec
23
comment is HttpOnly and Secure cookie enough to prevent CSRF in rest api?
Please use spell check and proper punctuation. English is hard, but at-least follow the basic rules when posting. Also, yes your app is vulnerable as hell.
Dec
23
revised is HttpOnly and Secure cookie enough to prevent CSRF in rest api?
OMFG SPELL CHECK