[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGSdRtiu_=JDghfezt977Dv3ukUF2vvTKPoDEx_TmKVhUSM8XA@mail.gmail.com>
Date: Wed, 8 Feb 2012 08:55:37 -0500
From: Luis Santana <hacktalkblog@...il.com>
To: b <b@...isoryalerts.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: posting xss notifications in sites vs
software packages
Typically you will run into instances where a website is employing a custom
CMS/plugin/module/whatever and as such there may not be a specific software
to call out as the one at fault.
It's like finding an XSS in Microsoft, 99% chance they are running their
own custom CMS so at that point you are just left with saying that
Microsoft is vulnerable to XSS as there is no name to the software at hand.
On Tue, Feb 7, 2012 at 6:18 PM, b <b@...isoryalerts.com> wrote:
> What is the point of posting notifications of XSS vulnerabilities in
> specific web sites instead of alerts of xss vulns in specific software
> packages?
>
> This question was prompted by all the postings by that vulnerability lab
> stuff.
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>
Content of type "text/html" skipped
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists