01-08-2018 02:30 PM - edited 03-20-2019 09:48 PM
Hi CISCO ,
I believe the list of affected release is incomplete. I have had to open a TAC Support Case to confirm this and I was informed by the TAC Engineer that all other releases from 2.2(6)B are also affected by the vulnerability. It would be good if CISCO could update the list of the affected releases.
Solved! Go to Solution.
01-08-2018 08:00 PM
I am aware of that. My point is that CISCO bug id does not indicate that all other versions are impacted. I was able to see the details of the bug earlier - CSCvg97979. Initially it listed 2.2(0.6) B as the affected release. However , the link to the bug ID is not available.
Anyways , thank you for the response.
01-10-2018 12:11 PM
01-08-2018 03:09 PM
01-08-2018 08:00 PM
I am aware of that. My point is that CISCO bug id does not indicate that all other versions are impacted. I was able to see the details of the bug earlier - CSCvg97979. Initially it listed 2.2(0.6) B as the affected release. However , the link to the bug ID is not available.
Anyways , thank you for the response.
01-10-2018 12:11 PM
01-10-2018 01:59 PM
Thank you. Company is going through PCI Compliance review. This bit light's up like a like Christmas Tree in the compliance report. Its good that CISCO has a release date for the fix.
01-15-2018 11:10 AM
Any idea why Cisco is requiring that much time to provide the release? Most major server vendors have already released patches for CVE-2017-5715 mitigation. I have multi-user systems so this is fairly critical.
01-15-2018 11:41 AM
@hostasaurus wrote:
I have multi-user systems so this is fairly critical.
Reach out to your Cisco SE/AM and they should be able to provide more information.
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