Hiki session ID security bypass
| hiki-sessionid-security-bypass (35029) |  Medium Risk |
Description:
Hiki could allow a remote attacker to bypass security restrictions, caused by the improper checking of a session ID which is used as a filename of a file that is deleted during the logout process. By specifying a specially-crafted session ID, a remote attacker could exploit this vulnerability to bypass security restrictions and delete arbitrary files on the vulnerable system.
Platforms Affected:
- Debian, Debian Linux 4.0
- Hiki, Hiki 0.8.0 - 0.8.6
Remedy:
Refer to Hiki Advisory 2007-06-24 for patch, upgrade, or suggested workaround information. See References.
For Debian/GNU Linux:
Refer to DSA-1324-1 for patch, upgrade, or suggested workaround information. See References.
For other distributions:
Contact your vendor for upgrade or patch information.
Consequences:
Bypass Security
References:
- Hiki Advisory 2007-06-24, Vurlnerability in Hiki - arbitrary file delete at http://hikiwiki.org/en/advisory20070624.html.
- BID-24603: Hiki Session ID File Deletion Vulnerability
- CVE-2007-2836: Directory traversal vulnerability in session.rb in Hiki 0.8.0 through 0.8.6 allows remote attackers to delete arbitrary files via directory traversal sequences in the session ID, which is matched against an insufficiently restrictive regular expression before it is used to construct a filename that is marked for deletion at logout.
- DSA-1324: hiki -- missing input sanitising
- SA25764: Hiki Session ID Arbitrary File Deletion Security Issue
- VUPEN/ADV-2007-2304: Hiki session.rb Session ID Processing Arbitrary File Deletion Vulnerability
Reported:
Jun 24, 2007
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net