Forum Discussion

Scott_McRoberts's avatar
Scott_McRoberts
Icon for Nimbostratus rankNimbostratus
Mar 18, 2019

F5 SIRT Security Alerts

When receiving F5 SIRT Security Alerts and you click the link like this one: https://support.f5.com/csp/article/K97241515

 

And the Article says FINAL and then: The security issue described in this article has either been resolved or does not affect any F5 products. There will be no further updates, unless new information is discovered.

 

Is there anything that needs to be done for this alert, there are platforms and versions listed? I see several like this from time to time and want to make sure the correct process.

 

  • It says near the end of the article what would potentially need to be done:

     

    "Security Advisory Recommended Actions If you are running a version listed in the Versions known to be vulnerable column, you can eliminate this vulnerability by upgrading to a version listed in the Fixes introduced in column. If the table lists only an older version than what you are currently running, or does not list a non-vulnerable version, then no upgrade candidate currently exists."

     

    If you aren't effected by it, then there is nothing to do!

     

    Hope that helps! If it does, please up-vote and select this answer, it would be greatly appreciated!

     

    -Dylan

     

    • Scott_McRoberts's avatar
      Scott_McRoberts
      Icon for Nimbostratus rankNimbostratus

      no doesn't really answer my question, I usually do go ahead and check the recommended actions.

       

      But why do some alerts have this in all RED lettering and some don't: The security issue described in this article has either been resolved or does not affect any F5 products. There will be no further updates, unless new information is discovered.

       

      "has either been resolved or does not affect any F5 products."

       

    • Dylan_375544's avatar
      Dylan_375544
      Icon for Cirrocumulus rankCirrocumulus

      I infer if it doesn't have that, then the issue hasn't been resolved for all supported versions of BIG-IP yet, and they are still working on solutions.