[Owasp-topten] RFI taken out
ht at computerdefense.org
Tue Nov 17 10:51:04 EST 2009
>From my point of view, I was fairly neutral on the removal of
"Malicious File Execution" but I would like to continue a statement
I'd made previously on this list. If it continues to deserve a spot on
the list, this is the perfect time to roll XSS into Injection and open
up a spot. After all XSS, at a basic level, is just HTML Injection...
and if we've already got SQL Injection, LDAP Injection and OS Command
Injection, why not bring this one into the injection pile as well?
On Tue, Nov 17, 2009 at 4:55 AM, Ty Miller <tyronmiller at gmail.com> wrote:
> Hey guys,
> You know this comment would be coming (if it hasn't already and I
> missed it) ... But, here goes ... and to put it clearly so there are
> no misunderstandings ...
> "What were you guys smoking when you took RFI out of the top 10???"
> I understand that RFI mainly affects php about 99.99% of the time, but
> this vuln is out there and organisations are getting smashed with it.
> I am the CTO of a pen testing company who also does digital forensics
> when clients ring up in a panic saying "OMG, we've been hacked! What
> do we do?"
> The top two ways that organisations were being hacked via their web
> apps that we saw was SQLi followed very closely by RFI.
> I was expecting this vuln to be moved up the ranks, especially when I
> read about the focus being more concentrated on the risk rather than
> how common the vuln is ... But to my extreme suprise, it was gone!
> If I had the choice between RFI and XSS to exploit and weigh up the
> risks, RFI would win hands down.
> BTW, doc looks good.
> Owasp-topten mailing list
> Owasp-topten at lists.owasp.org
More information about the Owasp-topten