Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 27 Feb 2012 11:28:35 +0100
From: Rafał Malinowski <>
Cc: "Steven M. Christey" <>, Mariusz Fik <>, 
	Radoslaw Lisowski <>,
Subject: Re: CVE Status Clarification / Request -- kadu: Stored XSS by parsing
 contact's status and sms messages in history


I'm forwarding this mail to bug reported, Mateusz Goik
( He said that he will take care of CVE identifier
after Kadu 0.11.1 is released (it is available since late Saturday).


W dniu 27 lutego 2012 11:05 użytkownik Jan Lieskovsky
<> napisał:
> Hello Mariusz, Kurt, Steve, vendors,
>  [1] though
>  mentions CVE identifier has been already requested for this:
>  "The bug still doesn't have CVE number but will have in near future."
>  it doesn't look like CVE id has been requested for this via OSS
>  security list, so moving this discussion / CVE request there.
>  Mariusz, could you clarify, if this issue has got a CVE identifier
>  already or if we still need one? If aren't able to do so, whom
>  should we contact to be clear about "CVE request status" for this?
>  Or at least clarify which list that "Here is a part of massage sent
>  by developers to package maintainers:" has been sent to? (so
>  we could ask there)
>  And in the end either use that one, already allocated or allocate
>  a new one here via OSS.
>  Below being issue description as I got it based on / from [2]:
>  A stored cross-site scripting (XSS) flaw was found in the way Kadu, the
> instant
> messenger compatible with the Gadu-Gadu protocol, performed sanitization of
> status and sms messages for particular contact in user's history. A remote
> attacker could provide a specially-crafted status or sms message, which
> would
> be stored in victim's Kadu history file, if the attacker was present on the
> contact list of the victim and the victim has had storage of statuses
> enabled
> for their history file. When the victim later examined the content of the
> status history, this flaw could lead to arbitrary HTML or webscript
> execution.
> References:
> [2]
> [3]
> Upstream patches:
> [4]
>    (patch for the XSS issue)
> [5]
>    (additional hardening)
> [6]
>    (disable xhtmlrequests)
> [7]
>   (allow only GET and HEADER requests, additional hardening)
> Thank you && Regards, Jan.
> --
> Jan iankko Lieskovsky / Red Hat Security Response Team

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.