under what conditions does security focus update vulnerabilities?

[Thomas Anderson <zelnaga () gmail com>]

I just received an entry for a vulnerability that was patched over
four years ago on my securityfocus.com RSS feed.  Specifically, this
one:

http://www.securityfocus.com/bid/13545

As per that page, it was fixed with 2.0.15, with 2.0.15 being released
on May 7, 2005:

http://www.phpbb.com/community/viewtopic.php?f=14&t=288194

Indeed, not only is it four years old but it's for a product that is
now considered deprecated:

http://www.phpbb.com/community/viewtopic.php?f=14&t=1385785

Presumably the reason I received notification was because it was
updated yesterday.  My question is...  why?  If updating a
vulnerability causes you to be notified about it as though it were new
then maybe vulnerability updates ought not appear on the
securityfocus.com mailing list?  I couldn't care less about a
vulnerability that's been known about for four years.

I do think providing notifications when a vulnerability is RETIRED is
still prudent, but for some random unspecified update?  I mean, what's
next?  Am I going to start receiving vulnerability notifications
regarding 15-year old vulnerabilities in Windows 3.0?

------------------------------------------------------------------------
Securing Apache Web Server with thawte Digital Certificate
In this guide we examine the importance of Apache-SSL and who needs an SSL certificate.  We look at how SSL works, how 
it benefits your company and how your customers can tell if a site is secure. You will find out how to test, purchase, 
install and use a thawte Digital Certificate on your Apache web server. Throughout, best practices for set-up are 
highlighted to help you ensure efficient ongoing management of your encryption keys and digital certificates.

http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be442f727d1
------------------------------------------------------------------------