Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Security-Basics
[Top] [All Lists]

Re: What does it mean for a vulnerability to be retired?

Subject: Re: What does it mean for a vulnerability to be retired?
Date: Fri, 21 Dec 2007 13:33:40 -0500 (Eastern Standard Time)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Under the "Discussion" tab for this securityfocus.com BID is the
note:

"NOTE: This BID is being retired because information provided by the
 vendor reveals that the application is not vulnerable to this issue."

Extrapolating from this sampling of one, I'd bet that RETIRED is
fairly rarely used.

   -g

- --
Glenn Forbes Fleming Larratt
Cornell University IT Security Office

On Fri, 21 Dec 2007, Terra Frost wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

<http://www.securityfocus.com/bid/26885> is an example of a
vulnerability whose status has been changed to RETIRED.  My question
is..  what, exactly, does that mean?

My guess is that it means that the vulnerability is bogus.  But why,
then, say it's RETIRED and not BOGUS?  It's hard to misinterpret BOGUS,
but rather easy to misinterpret RETIRED.

Further, if that is indeed what RETIRED means, why would the above
report, under "Vulnerable", say "WordPress", when, in fact, it isn't?
Maybe, if anything, it should say WordPress and then have a
strikethrough through it?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHbAHOhzLeabOflWcRAnJMAJoCmRiHYnmOLgjywLPn/RQHs4RWOwCdGreH
wIJDT6A+rtFf/KXkg8Icsis=
=Qtls
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFHbAcKLyw7nZwiKgQRAlmYAKD3IWMYKa4ostdxF5dJiAL01I8roACfYVfV
dbauyYdeNbBrNeQCxZwiqw8=
=OAht
-----END PGP SIGNATURE-----

<Prev in Thread] Current Thread [Next in Thread>