full-disclosure - Command Injection Vulnerability in stat.qwest.net

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <3F464272.1090204@thievco.com>
From: BlueBoar at thievco.com (Blue Boar)
Subject: Command Injection Vulnerability in stat.qwest.net
 - OFFTOPIC

Kurt Seifried wrote:

> Why are you telling us this? How does it affect anyone, but qwest, who you
> notified, and who fixed it. Do we now send out a security advisory every
> time we notify sometime to disable a vulnerable service (sir, you have
> telnet enabled). This is getting ridiculous.

Couple of points:  It may be nice to know the track record of a company 
even though the problem has been fixed.  Also, QWest isn't the only ISP 
that uses Looking Glass...

						BB