I just read through the PHP Zend Certified Engineer study guide, and found at least 5 questions that have at least partially incorrect answers. (1 was grossly incorrect)
Escaping output may help protect from which common security
vulnerabilities? (Choose 2)
A: Clickjacking
B: Cross-Site Scripting
C: Cross-Ste Request Forgery
D: SQL Injection
The answer it says is B and D
But I stand that B and C are correct, since all XSS vulnerabilities are autoamtically CSRF vulnerabilities
@ircmaxell it's also imperative that you lock the door to the bank to prevent people from stealing money. that doesn't mean that opening the door is stealing.
@ircmaxell I don't disagree with that. My point is that those are two different attack vectors, even if they can be used together. (I also agree that the question sucks, by the way)
Well, but let's look at something more traditional
A buffer overflow can be used for arbitrary code execution. Does that mean that it's wrong to say that without securing all buffers you might be susceptible to arbitrary code execution? They are 2 different attack vectors, but one can enable the other.
@ircmaxell Sure, but ensuring that you've dealt with all buffer overflows doesn't necessarily mean that you're protected from arbitrary code execution.
@ircmaxell Yes, and that explains why that test questions sucks (which I agree with). But it doesn't say that code execution is a subset of buffer overflow exploits or the other way around.
So if they say output encoding protects against sql injection, they a) consider sql commands to be output, and b) encourage to forget the whole parametrization idea. Am I reading that right?
Android is incredible, I'm loving it... Never had an easier more enjoyable OS.
Ah, well then you have to get involved, rooted, and start flashing things. I'm running a rom called SuperClean 2.9.1, and it doesn't have any bloated crap from samsung or verizon.
Plus it's Froyo, which still hasn't been released officially for the Fascinate.
For those reading the transcript, this conversation has moved to another part of the interwebs, allegedly protected by SSL, passwords and ultimately, big brother Google.