The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
* Kernel: NetLabel: null pointer dereference while receiving CIPSO packet with null category may cause kernel panic (CVE-2020-10711)
More information can be found in the security advisory issued by Red Hat:
For assessment and severity classification details refer to Section 3 of Avaya's Product Vulnerability Response Policy.
The "Resolution" column will be updated as fixes are made available. Please reference the "Information" column for any additional information regarding the affected product.
| Product: | Version(s): | Resolution: | Information: |
|---|---|---|---|
| Avaya Aura® Application Enablement Services | 7.0.x | Upgrade to 7.1.3 and install LSU9 or upgrade to 8.1.2 and install LSU2 or later. | Avaya Aura® R7 is EOMS and this issue is addressed in a supported version, refer to Avaya Aura® Release 7 End of Manufacture Support. For 7.1.3.x LSU For 8.1.x LSU |
Avaya Aura® Application Server 5300:
|
3.0 SP11 through 3.0 SP15.3 | Upgrade to 3.0 SP15.4 or later. | |
| Avaya Breeze™ Platform | 3.0 through 3.2.x | Upgrade to 3.8 or later. | |
| Avaya CMS | R18 through R18.1.0.3 | Upgrade to R18.1.0.4 or R19.2 or later. | R17 is EOMS and this issue will be addressed in a supported version, refer to the End of Sale Notice. |
| Avaya Aura® Communication Manager | 7.0.x | Upgrade to latest version of 7.1.x and install Kernel Service Pack 10 or upgrade to latest version of 8.1.x and install Kernel Service Pack 5 or later. | Avaya Aura® R7 is EOMS and this issue is addressed in a supported version, refer to Avaya Aura® Release 7 End of Manufacture Support. 7.1.x Kernel Service Pack 8.1.x Kernel Service Pack |
| Avaya Aura® Communication Manager Messaging | 7.0.x | No further releases are planned. | See recommended actions below. This advisory will not be addressed as no further releases are planned. It is recommended to migrate to another Avaya Messaging solution such as Officelinx, Avaya Multimedia Messaging or Avaya Aura Messaging. Refer to the End of Sale Notice. |
| Avaya Aura® Conferencing | 8.0 through 8.0 SP17 | Upgrade to 8.0 SP18 or later. | |
| Avaya Aura® Experience Portal | 7.x | Upgrade to 7.2 and install latest security updates. | 7.2.x. |
| Avaya IP Office | 10.x, 11.0.x | Upgrade to 11.1.1.0 or later. | |
| Avaya Meeting Exchange | 6.2 SP3 through 6.2 SP9 | Upgrade to 6.2 SP10 or later. | |
| Avaya Aura® Messaging | 7.0.x | Upgrade to 7.1 and install Service Pack 3 or later. | |
| Avaya one-X® Client Enablement Services | 6.2 through 6.2.8 | Upgrade to 6.2.9 or later. | 6.2 SP9 and later versions are software-only.
Refer to:
|
| Avaya Proactive Contact | 5.2.x | No fix planned | |
| Avaya Session Border Controller for Enterprise | 7.0.x, 7.1.x, 7.2.0 | Upgrade to 7.2.1 or later. | |
| Avaya Aura® Session Manager | 7.0.x | Upgrade to 7.1.3.7 or 8.1.3.0 or later. | Avaya Aura® R7 is EOMS and this issue is addressed in a supported version, refer to Avaya Aura® Release 7 End of Manufacture Support. |
| Avaya Aura® System Manager | 7.0.x | Upgrade to 7.1.3.8 or 8.1.3.0 or later. | Avaya Aura® R7 is EOMS and this issue is addressed in a supported version, refer to Avaya Aura® Release 7 End of Manufacture Support. |
| Avaya Aura® Utility Services | 7.0.x | Upgrade to 7.1.3.8 or later. | Avaya Aura® R7 is EOMS and this issue will be addressed in a supported version, refer to Avaya Aura® Release 7 End of Manufacture Support. |
Recommended Actions for Products:
Avaya strongly recommends following networking and
security best practices by implementing firewalls, ACLs,
physical security or other appropriate access restrictions.
Though Avaya believes such restrictions should always be in
place, risk to Avaya products and the surrounding network
from this potential vulnerability may be mitigated by
ensuring these practices are implemented until such time as
an Avaya provided product update or the recommended Avaya
action is applied.
Further restrictions as deemed necessary based on the
customer's security policies may be required during this
interim period, but the System Product operating system or
application should not be modified unless the change is
approved by Avaya. Making changes that are not approved may
void the Avaya product service contract.
Avaya uses the Common Vulnerability Scoring System
(CVSS) base score and metrics as reported by the vendor for the affected component(s) or by the National Institute of Standards and Technology in the National Vulnerability Database. In some cases, such as where CVSS information is not available from the vendor or NIST, Avaya will calculate the CVSS base score and metrics. Customers are encouraged to calculate the Temporal and Environmental CVSS scores to determine how the vulnerability could affect their specific implementation or environment. For more information on CVSS and how the score is calculated, see
Common Vulnerability Scoring System: Specification Document.
| Vulnerability | CVSSv3 Base Score | CVSSv3 Metrics |
|---|---|---|
| CVE-2020-10711 |
5.9 (Medium) | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
Avaya software-only products operate on general-purpose operating systems. Occasionally, vulnerabilities may be discovered in the underlying operating system or applications that come with the operating system. These vulnerabilities may not impact the software-only product directly but may threaten the integrity of the underlying platform.
| Product: | Actions: |
|---|---|
| Avaya Aura® Application Enablement Services | If an affected package is installed, Avaya recommends following the actions supplied by Red Hat. |
| Avaya Aura® Experience Portal | If an affected package is installed, Avaya recommends following the actions supplied by Red Hat. |
| one-X Client Enablement Services | If an affected package is installed, Avaya recommends following the actions supplied by Red Hat. |
Additional information may also be available via the Avaya support website and through your Avaya account representative. Please contact your Avaya product support representative, or dial 1-800-242-2121, with any questions.
ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION, IS PROVIDED "AS IS", AND IS APPLICABLE ONLY TO PRODUCT VERSIONS ELIGIBLE FOR MANUFACTURER SUPPORT IN ACCORDANCE WITH AVAYA PRODUCT LIFE CYCLE POLICY. AVAYA INC., ON BEHALF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS "AVAYA"), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS' SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, INCIDENTAL, STATUTORY, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA.
V 1.0 - June 16, 2020 - Initial Statement issued.
V 2.0 - April 30, 2021 - Updated versions and resolutions for AES, Breeze, CMS, CM, Conferencing, EP, IPO, MX, Messaging, One-X CES, PC, SM, SMGR and US.
V 3.0 - December 8, 2021 - Updated Versions, Resolution, Information columns for all other products and set the Advisory status to Final.
Avaya customers or Business Partners should report any security issues found with Avaya products via the standard support process.
Independent security researchers can contact Avaya at
[email protected].
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 2020 Avaya Inc. All Rights Reserved. All trademarks identifying Avaya products by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.