Documentation forSecurity Event Manager

SEM 2021.2.1 Release Notes

Release date: June 15, 2021

Updated: June 22, 2021

This document summarizes new features, improvements, and fixed issues in Security Event Manager (SEM) 2021.2.1, additional features, and upgrade notes and workarounds for known issues.

For further information, see the SEM 2021.2 Administrator Guide.

For system requirements, see SEM 2021.2 System Requirements.

For releases prior to SEM 2021.2.1, see Previous Version documentation.

New in SEM 2021.2.1

SEM 2021.2.1 is a service release, containing the following improvement:

  • An issue has been resolved that was causing upgrades to fail on systems that had been running since version 5.2 or earlier.

See SEM 2021.2 Release Notes for new features in the SEM 2021.2 release.

New customer installation

For information about installing SEM, see the SEM Installation Guide and the SEM Getting Started Guide. For system requirements see the SEM 2021.2 System Requirements.

Before you upgrade

Migrate LDAP connectors (introduced in SEM 2020.4)

It is recommended that users remove any ambiguity in their Directory Service Tool connector configurations to allow migration to run as smoothly as possible. This can be by ensuring only one Directory Service Tool connector configuration is set up per domain.

All Directory Service Tool connectors are removed in process of the migration.

Upgrade agents

For AIX, HPUX and Solaris, agents installers now only contain custom Java; this means customers need to install Java themselves as a prerequisite.

  1. Upgrade Java installation to the latest version. See System Requirements for supported versions.
  2. Upgrade SEM agents using latest custom Java installer.

How to upgrade

If you are upgrading from a previous version, use the following resources to plan and implement your upgrade.

SEM  must be upgraded to 2020.2 or 2020.2.1 before upgrading to 2021.2.1. See the SEM Upgrade Path to help you plan and execute your upgrade.

Download the upgrade package from the SolarWinds Customer Portal.

CMC

Since SEM 2020.4, a password is required to access the CMC command-line interface. The default CMC password is password. See Change the SEM CMC password for instructions on changing this.

File system consistency check (fsck)

During your upgrade, the system may run a fsck check during reboot. This can last 30 or more minutes depending on the quantity of data in the data partition. With the Debian version upgrade, the file system is configured to initiate the check when certain conditions are met:

  • 21 mounts since the last check (during the 22nd reboot)

Or:

  • Six months since the last check

Supported connectors

The list of supported connectors can be found here.

Fixed issues

See SEM 2021.2 fixed issues.

Known issues

See SEM 2021.2 known issues.

CVE issues

SolarWinds would like to thank our Security Researchers below for reporting on the issue in a responsible manner and working with our security, product, and engineering teams to fix the vulnerability.

CVE-ID Vulnerability Title Description Severity Credit
CVE-2021-34437 Incorrect permission on SEM CMC shell can lead to privilege escalation The CMC account is vulnerable to privilege escalation using the CMC shell. This vulnerability allows the changing of the file permissions and overwrite of the file by the CMC user over SFTP. High Anthony Jones

End of life, end of support, and deprecation notices

End of life

Version

EOL

Announcements

EOE Effective

dates

EOL Effective dates
6.7 May 18, 2021: End-of-Life (EoL) announcement – Customers on SEM versions 6.7, 6.7.1, and 6.7.2 should begin transitioning to the latest version of SEM. August 18, 2021: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SEM versions 6.7, 6.7.1, and 6.7.2 will no longer be actively supported by SolarWinds. August 18, 2022: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SEM version versions 6.7, 6.7.1, and 6.7.2.
6.6 June 6, 2020: End-of-Life (EoL) announcement – Customers on SEM version 6.6 should begin transitioning to the latest version of SEM. September 6, 2020: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SEM version 6.6 will no longer be actively supported by SolarWinds. September 6, 2021: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SEM version 6.6.

End of support

Type Details
MSSQL Auditor

With SEM 2021.2, the MSSQL Auditor is no longer supported.

The MSSQL Auditor connector will remain available.

Standalone Adobe Air Console

See the Adobe Flash End-of-Life page (© 2021 Adobe, available at adobe.com, retrieved April 12, 2021).

Legal notices

© 2021 SolarWinds Worldwide, LLC. All rights reserved.

This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.