Skip to main content

SolarWinds Releases Security Update for Security Event Manager

Update addresses a vulnerability that could lead to RCE and 4 third-party vulnerabilities in SEM

Threat ID:
CC-4458
Threat Severity:
Medium
Published:
4 March 2024 4:46 PM
Report a cyber attack: call 0300 303 5222 or email [email protected]

Summary

Update addresses a vulnerability that could lead to RCE and 4 third-party vulnerabilities in SEM

Affected platforms

The following platforms are known to be affected:

Versions: prior to 2023.2.3

SolarWinds Security Event Manager (SEM)

Threat details

Introduction

SolarWinds has released a security update to address a deserialisation of untrusted data vulnerability in Security Event Manager (SEM), which is the SolarWinds version of a SIEM tool. An unauthenticated attacker could exploit this vulnerability by abusing SolarWinds' service, leading to remote code execution (RCE). This vulnerability is rated as high with a CVSSv3 score of 8.8.

The update also addresses 4 third-party vulnerabilities:

  • CVE-2023-48795        Terrapin-Attack Vulnerability              CVSSv3 score - 5.9 Medium
  • CVE-2023-3961          Path Traversal Vulnerability                 CVSSv3 score - 9.8 Critical
  • CVE-2023-4154          Broken Access Control Vulnerability   CVSSv3 score - 6.5 Medium
  • CVE-2023-42670        Denial of Service Vulnerability            CVSSv3 score - 6.5 Medium

Remediation advice

Affected organisations are encouraged to review the SolarWinds security advisory for CVE-2024-0692, the SEM 2023.4.1 release notes, and apply any necessary updates. 

CVE Vulnerabilities

Status Published

CVE-2024-0692

The SolarWinds Security Event Manager was susceptible to Remote Code Execution Vulnerability. This vulnerability allows an unauthenticated user to abuse SolarWinds' service, resulting in remote code execution.
Status Published

CVE-2023-48795

The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in [email protected] and (if CBC is used) the [email protected] MAC algorithms. 
Status Published

CVE-2023-3961

A path traversal vulnerability was identified in Samba when processing client pipe names connecting to Unix domain sockets within a private directory. Samba typically uses this mechanism to connect SMB clients to remote procedure call (RPC) services like SAMR LSA or SPOOLSS, which Samba initiates on demand. 
Status Published

CVE-2023-4154

A design flaw was found in Samba's DirSync control implementation, which exposes passwords and secrets in Active Directory to privileged users and Read-Only Domain Controllers (RODCs). This flaw allows RODCs and users possessing the GET_CHANGES right to access all attributes, including sensitive secrets and passwords. Even in a default setup, RODC DC accounts, which should only replicate some passwords, can gain access to all domain secrets, including the vital krbtgt, effectively eliminating the RODC / DC distinction. Furthermore, the vulnerability fails to account for error conditions (fail open), like out-of-memory situations, potentially granting access to secret attributes, even under low-privileged attacker influence.
Status Published

CVE-2023-42670

A flaw was found in Samba. It is susceptible to a vulnerability where multiple incompatible RPC listeners can be initiated, causing disruptions in the AD DC service. When Samba's RPC server experiences a high load or unresponsiveness, servers intended for non-AD DC purposes (for example, NT4-emulation "classic DCs") can erroneously start and compete for the same unix domain sockets. This issue leads to partial query responses from the AD DC, causing issues such as "The procedure number is out of range" when using tools like Active Directory Users. This flaw allows an attacker to disrupt AD DC services.

Last edited: 4 March 2024 4:46 pm