Need Corresponding Release of Vulnerabilities Fixed by Recently Released Patches/Fix Packs

There needs to be planned release(s) of known security vulnerabilities that are addressed in recent patches, i.e. 6.1.2.4 through regular channels (subscribed notifications). That seems to be how they've been released for IBM Sterling products in the past, but the information is a bit scattered over multiple bulletins sent out over time (usually a few weeks after release of the patch) based on subscribed notifications. Recently there was a list of 31 fixed vulnerabilities in fix pack release 6.1.2.4. That's great, and I completely understand that in a fix list not an appropriate place to list what these vulnerabilities are since it's public information, but the information needs to be published up to OpenCVE to correspond with the release of software so their scores are identified and customers of B2Bi/SFG can notify their security teams of what the vulnerabilities are that are addressed. DB2 as an example mostly does a pretty good job of this. Some customer/host sites run regular vulnerability scans, but it seems there isn't a way to reconcile against what vulnerability applications like QUALYS might come up with in their scans of B2Bi across its ports and access points without opening potentially a plethora of cases.

If there are vulnerabilities with a CVSS of 7 or above, I need to address those as high priority (for upgrade). Otherwise my B2Bi clusters/instances sit vulnerable until I find out one way or the other; either I'm hacked because I can't get the information I need even though I AM subscribed or I get lucky and exploits aren't used to harvest information, depending on the score assigned to each vulnerability and ability to exploit it. As we've all seen with the MOVEIt hack that reared its ugly head recently, I wouldn't want to see IBM's reputation suffer because customers couldn't get the vulnerability information and mitigate it with an existing fix pack.

Also I shouldn't be applying patches out of superstition. Informed decision making is always better. Since we manage many servers with IBM Sterling software on them, having this information available is critical to day-to-day operations and helps us prioritize builds and application of patches.