|
Source: Securiteam - Posted by Benjamin D. Thomas
|
There are three fairly interesting flaws in how HTTP cookies were designed and later implemented in various browsers; these shortcomings make it possible (and alarmingly easy) for malicious sites to plant spoofed cookies that will be relayed by unsuspecting visitors to legitimate, third-party servers.
Let's begin with a quick primer on cookie parsing: when a new cookie is issued to the browser (via "Set-Cookie" header in a HTTP response), the server is expected to specify the domain and URI for which the cookie is meaningful. This mechanism is present so that pages could limit the scope of their cookies if needed, and prevent the data from being sent to unrelated addresses in the same domain. For security purposes, the browser will (theoretically) reject a cookie that is set for a domain that is either defined too broadly, or does not match issuer's location at all.
Read this full article at Securiteam
Only registered users can write comments.
Please login or register. Powered by AkoComment! |
