|
BugTraq
Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data Mar 29 2006 03:22AM Jasper Bryant-Greene (jasper album co nz) (3 replies) Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data Apr 03 2006 02:06PM Moriyoshi Koizumi (moriyoshi at wakwak com) (1 replies) Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data Apr 03 2006 09:58PM Jasper Bryant-Greene (jasper album co nz) Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data Mar 29 2006 04:43PM Jeff Rosowski (rosowskij ie ymp gov) (1 replies) Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data Apr 04 2006 01:29PM John Bond (john r bond gmail com) |
|
Privacy Statement |
> I very much doubt there are many applications at all containing code
> like this. It is illogical to be decoding html entities from user
> input. Therefore I would not call this a "very serious problem" and
> certainly not a critical bug.
Somewhat I agree. I suspected this may affect more functions that only
this one and was very alarmed. I never digged around in PHP source and
was not able to verify it fast. So if PHP developer says, it is affects
only on function, this is fine.
There are application which are known to use it. Like
http://www.phpmyfaq.de/, so I attacker may use social engineering easily
to gain access to such feature.
I am security auditor and 90% cases I get to goal combining using bunch of small, useless problems. Sorry if you do not see problem.
EOD :).
[ reply ]