Avaya has posted several responses on support.avaya.com/security. Unfortunately, since this pesky bug has already resulted in Microsoft and VMware pulling patches I wouldn't expect any fix soon. Especially if the performance hit is as significant as some of the initial anecdotal information suggests.
Avaya's position on it appears to remain the same as when the vulnerabilities were first announced. They seem to be relying on OS patching to mitigate the issue while also stating that OS patching can cause other issues.
The issue boils down to the flaw being within the processor. This requires a bios/microcode update. So far, Microsoft, VMware, and Red Hat have pulled the initial patch releases due to a combination of bricked systems, reboots, and performance issues.
I expect Avaya will not be releasing patches soon. Once a stable patch exists at the OS level then Avaya will have to test. My understanding is the most significant performance hits will be for systems with high I/O. Since voice is a real-time service I expect significant hits which will require Avaya to either discontinue support for certain hardware (old Common Server Gen 1), modify the resource requirements, or alter the "stated" capacity of systems.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.