Re: Top Ten PHP Security Issues, a preliminary list
From: Chung Leong (chernyshevsky_at_hotmail.com)
Date: 02/14/04
- Next message: Chung Leong: "Re: tracking pixel in a processing script, instead of HTML page"
- Previous message: Chung Leong: "Re: Top Ten PHP Security Issues, a preliminary list"
- In reply to: Jochen Daum: "Re: Top Ten PHP Security Issues, a preliminary list"
- Next in thread: Alex Farran: "Re: Top Ten PHP Security Issues, a preliminary list"
- Reply: Alex Farran: "Re: Top Ten PHP Security Issues, a preliminary list"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 13 Feb 2004 18:52:21 -0500
Hi Jochen!
Uzytkownik "Jochen Daum" <jochen.daum@cans.co.nz> napisal w wiadomosci
news:qd9o20165r0aopi8buk6j2s2opvchbdokn@4ax.com...
> Other decisions, such as security against SQL injection need to be
> made on content, because people might wanna run a forum about SQL
> injection code. Again, why not require the user to log in.
The user is logged in. The problem is that the attacker can control his
browser using Javascript and do nasty things as him.
I guess a better solution to this problem would be to require the
accompaniment of an unique id, stored in a hidden, with every POST. The
receiving script would check the id posted against then one stored in the
session, and rejects the request if they don't match. That requires fixing
every form though. Checking the referrer is much easier.
- Next message: Chung Leong: "Re: tracking pixel in a processing script, instead of HTML page"
- Previous message: Chung Leong: "Re: Top Ten PHP Security Issues, a preliminary list"
- In reply to: Jochen Daum: "Re: Top Ten PHP Security Issues, a preliminary list"
- Next in thread: Alex Farran: "Re: Top Ten PHP Security Issues, a preliminary list"
- Reply: Alex Farran: "Re: Top Ten PHP Security Issues, a preliminary list"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|