05-25-2017 06:26 AM - edited 03-19-2019 12:28 PM
Does anybody know if 10.5(2)SU4 (10.5.2.14900-16) is affected by this bug? It's not listed in the Known Affected Releases table.
05-25-2017 07:04 AM
It certainly doesn't show, but then it tells you it was fixed until SU5
This vulnerability is fixed in 10.5(2)su5 and 11.0(1a)su3.
05-25-2017 07:15 AM
I have just upgraded from 10.5.2.13900-12 to 10.5.2.14900-16 (SU4) as per Cisco recomendations and its working fine.
05-18-2018 06:56 AM
I'm running 10.5.2.14900-16 (SU4) and this vulnerability is still showing on scans.
05-18-2018 08:00 AM
Because the fix is not in SU4, did you review the fixed releases in the bug?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide
Log in to Community
