|
|
|
>>
VUPEN Security / Public Mailing Lists Mirror |
Assigned : VUPEN/ADV-2006-0320
From : karmaguedon at hotmail.com
Subject : Claroline 1.7.2, sso identification vulnerability
Date : 2006-01-20
Original Message
hi,
this is what we can read in file "/claroline/inc/claro_init_local.inc.php" :
[...]
$ssoCookieValue = md5( mktime() );
$sql = "UPDATE `".$tbl_sso."`
SET cookie = '".$ssoCookieValue."',
rec_time = NOW()
WHERE user_id = ". (int) $_uid;
$affectedRowCount = claro_sql_query_affected_rows($sql);
if ($affectedRowCount < 1)
{
$sql = "INSERT INTO `".$tbl_sso."`
SET cookie = '".$ssoCookieValue."',
rec_time = NOW(),
user_id = ". (int) $_uid;
claro_sql_query($sql);
}
$boolCookie = setcookie($ssoCookieName, $ssoCookieValue,
$ssoCookieExpireTime,
$ssoCookiePath, $ssoCookieDomain);
[...]
so, the cookie value must be always unknown.
in this code, the cookie value is the md5 value of the connection time ! really unknown ? no.
solution :
desactivate sso service
or
replace mktime() by rand(100,1000000) (for e.g)
Disclaimer : VUPEN Security does not endorse the content of this
message submitted by others to public mailinglists. Messages submitted to public
mailinglists do not necessarily reflect the opinions or policies of VUPEN Security.
VUPEN Security makes no warranties, express or implied, as to the content of the message
in this page or the accuracy and reliability of any messages and other materials
submitted to public mailinglists. Any questions or comments regarding this page
should be sent to
team@vupen.com
|
|
|
|
|
|
Monthly Statistics |
 |
|
|
|
| |
|
Try VUPEN
VNS |
 |
|
 |
|
| |
|
 |
| |
|
|
|
|
