Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 10 Nov 2012 06:54:46 -0500 (EST)
From: Jan Lieskovsky <>
Cc: "Steven M. Christey" <>,
        Michel Alexandre Salim <>,
        Richard Jones <>,
        Ralf Schlatterbeck <>
Subject: Re: CVE Request -- roundup: Multiple XSS flaws plus other security
 related fixes corrected in upstream 1.4.20 version

Just to clarify the need for CVE ids. Looks roundup 1.4.20
has been released 15-May-2012 10:49:

but there doesn't seem to be CVE identifiers for these:


Thank you && Regards, Jan.
Jan iankko Lieskovsky / Red Hat Security Response Team

----- Original Message -----
Hello Kurt, Steve, vendors,

  Roundup upstream has released new upstream 1.4.20 version,
correcting multiple cross-site scripting (XSS) flaws (and
couple of other security related issues):

More from [1] (plus relevant tickets inlined too, where
possible to find out):
[A] * issue2550729: Fix password history display for anydbm backend,
thanks to Ralf Hemmecke for reporting. (Ralf)

[B] * issue2550684 Fix XSS vulnerability when username contains HTML code,
thanks to Thomas Arendsen Hein for reporting and patch. (Ralf)

[C] * issue2550711 Fix XSS vulnerability in @action parameter,
thanks to "om" for reporting. (Ralf)

[D] * Fix wrong execute permissions on some files,
thanks to Cheer Xiao for the patch. (Ralf)

[E] * Fix another XSS with the "otk" parameter,
thanks to Jesse Ruderman for reporting. (Ralf)

[F] * Mark cookies HttpOnly and -- if https is used -- secure. Fixes issue2550689,
but is untested if this really works in browsers. Thanks to Joseph Myers for reporting. (Ralf)

[G] * Fix another XSS with the ok- and error message, see issue2550724. We solve this differently
from the proposals in the bug-report by not allowing any html-tags in ok/error messages
anymore. Thanks to David Benjamin for the bug-report and to Ezio Melotti for several proposed fixes. (Ralf)

Cc-ed Ralf Schlatterbeck on this post too to clarify, if issues [A] and [D]
would also have security implications / IOW if those would be security flaws too.
Ralf please clarify. Thank you, Jan.

Could you allocate CVE ids for these (once clarified)?

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.