Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 5 Jan 2015 20:13:29 +0200
From: Henri Salo <>
To: Korvin Szanto <>
Cc:, Simo Ben youssef <>
Subject: Re: CVE request: Concrete5 XSS vulnerability

Hash: SHA1

On Mon, Jan 05, 2015 at 09:56:24AM -0800, Korvin Szanto wrote:
> This has been fixed in 5.7.3 for some time
> We have a security disclosure program for this so any disclosure
> outside of our program is very irresponsible and unprofessional. You
> end up with outdated information and leave us unable to fix the issue
> in a secure way since we cannot see it until it's brought to our
> attention through our disclosure program.

Original advisory in says following:

Disclosure time-line
02 November 2014: Discovery.
03 November 2014: Initial report sent.
11 November 2014: Second contact.
No response.
09 December 2014: Public disclosure.

I do not know how author of that advisory tried to contact Concrete5. For
future cases:

I only requested CVE for coordination purposes. In this case CVE is used to
notify end-users to actually update their software so that they are not affected
by this vulnerability. If you want more details please contact me off-list.

Would it be possible for Concrete5 to request CVEs in the future as part of your
security disclosure program?

- -- 
Henri Salo
Version: GnuPG v1.4.12 (GNU/Linux)


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.