http://drupal.ro/node/2060
"Security: allow html posts creates security issue via stolen cookies, is that right?
* drupal 4.7
* How To Drupal
* post installation
I was planning to let users use html format.I'm reading wikipeda about security
According to this article
http://en.wikipedia.org/wiki/HTTP_cookieit seems that lettings users post content in html format creates a problem: cookies can be stolen and used to log in. encryption does not help. the only way to address this is by disabling html format.Cross-site scripting allows the value of cookies to be sent to servers that are normally not sent these values. Modern browsers allow execution of pieces of code retrieved from the server. If cookies are accessible during execution, their value may be communicated in some form to servers that should not access them. The process allowing an unauthorised party to receive a cookie is called cookie theft, and encryption does not help against this attack.[10]
This possibility is typically exploited by attackers on sites that allow users to post HTML content. By embedding a suitable piece of code in an HTML post, an attacker may receive cookies of other users. Knowledge of these cookies can then be exploited by connecting to the same site using the stolen cookies, thus being recognised as the user whose cookies have been stolen.have I understood this correctly? I will disable html format if necessary.
* autentifică-te sau ?nregistrează-te pentru a adăuga comentarii"
http://www.derkeiler.com/Mailing-Lists/VulnWatch/2006-07/msg00019.html
"[VulnWatch] Corsaire Security Advisory - VMware ESX Server Password Disclosure in Cookie issue
* From: "advisories"
* Date: Mon, 31 Jul 2006 13:59:57 +0100
-- Corsaire Security Advisory --
Title: VMware ESX Server Password Disclosure in Cookie issue
Date: 12.05.06
Application: VMware ESX prior to 2.5.2 patch 4
VMware ESX prior to 2.0.2
Environment: VMware ESX
Author: Martin O'Neal [martin.oneal@xxxxxxxxxxxx]
Audience: General distribution
Reference: c060512-001
-- Scope --
The aim of this document is to clearly define an issue that exists with
the VMware ESX Server product [1] that will allow a local attacker to
gain access to users' (including root's) passwords under certain
conditions.
-- History --
Discovered: 12.05.06 (Martin O'Neal)
Vendor notified: 19.05.06
Document released: 31.07.06
-- Overview --
VMware ESX Server is described [1] as virtual infrastructure software
for partitioning, consolidating and managing servers in mission-critical
environments.
The software provides a virtualization layer that allows multiple x86
based operating systems to run on the same hardware concurrently. The
ESX Server product differs from other VMware products in that it does
not require a "host" operating system to be provided by the user.
Instead, it uses a custom x86 kernel as the host, along with a
customised Linux operating system as a "console O/S".
VMware ESX Server includes a number of network services and a web
application, called the "VMware Management Interface" that can be used
to perform remote administration of the system.
-- Analysis --
The Management Interface is a traditional web application, which
utilises a session ID contained within two cookies; vmware.mui.kid and
vmware.mui.sid. The Session ID format is proprietary and contains the
user account and password in a simple (recursively) base64 encoded
format.
If an attacker can gain access to the cookies by any mechanism, such as
through a simple cross site scripting attack, then they will acquire not
only the session ID, but the authentication credentials as well.
-- Recommendations --
Upgrade to a version of the VMware ESX product that does not exhibit
this issue.
-- CVE --
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2006-2481 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org), which standardises names for
security problems.
-- References --
[1] http://www.vmware.com/products/esx/
-- Revision --
a. Initial release.
b. Minor edits.
c. Released.
-- Distribution --
The information contained within this advisory is supplied "as-is" with
no warranties or guarantees of fitness of use or otherwise. Corsaire
accepts no responsibility for any damage caused by the use or misuse of
this information."
Just two of many. Defcon routinely has presentations on cookie hijacking. The Use of cookie hijacking has most recently been used to access banking information; that is, if you follow MilWorm and a few other sites.