CyberSecBulletin
CVE-2023-4606NVD status: Modified

Lenovo XClarity Controller (XCC): Missing Authorization

CVE-2023-4606 is a high-severity missing authorization vulnerability in Lenovo XClarity Controller (XCC) from Lenovo, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected Lenovo XClarity Controller (XCC) versions: various. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.56% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of Lenovo XClarity Controller (XCC) you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on support.lenovo.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
LenovoLenovo XClarity Controller (XCC)variousNot stated
LenovoThinkagile Hx5530 FirmwareNot specified in the recordNot stated
LenovoThinkagile Hx7530 FirmwareNot specified in the recordNot stated
LenovoThinkagile Vx3331 FirmwareNot specified in the recordNot stated
LenovoThinkagile Hx1331 FirmwareNot specified in the recordNot stated
LenovoThinkagile Hx2330 FirmwareNot specified in the recordNot stated
LenovoThinkagile Hx2331 FirmwareNot specified in the recordNot stated
LenovoThinkagile Hx3330 FirmwareNot specified in the recordNot stated
LenovoThinkagile Hx3331 FirmwareNot specified in the recordNot stated
LenovoThinkagile Hx3375 FirmwareNot specified in the recordNot stated
LenovoThinkagile Hx3376 FirmwareNot specified in the recordNot stated
LenovoThinkagile Hx5531 FirmwareNot specified in the recordNot stated
LenovoThinkagile Hx7531 FirmwareNot specified in the recordNot stated
LenovoThinkagile Mx3330-f All-flash FirmwareNot specified in the recordNot stated
LenovoThinkagile Mx3330-h Hybrid FirmwareNot specified in the recordNot stated
LenovoThinkagile Mx3331-f All-flash FirmwareNot specified in the recordNot stated
LenovoThinkagile Mx3331-h Hybrid FirmwareNot specified in the recordNot stated
LenovoThinkagile Mx3530 F All Flash FirmwareNot specified in the recordNot stated
LenovoThinkagile Mx3530-h Hybrid FirmwareNot specified in the recordNot stated
LenovoThinkagile Mx3531 H Hybrid FirmwareNot specified in the recordNot stated
LenovoThinkagile Mx3531-f All-flash FirmwareNot specified in the recordNot stated
LenovoThinkagile Vx2330 FirmwareNot specified in the recordNot stated
LenovoThinkagile Vx3330 FirmwareNot specified in the recordNot stated
LenovoThinkagile Vx3530-g FirmwareNot specified in the recordNot stated
LenovoThinkagile Vx5530 FirmwareNot specified in the recordNot stated

Version data comes from the organisation that assigned the CVE; 34 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.1HighCNA (lenovo.com)
CVSS 3.18.1HighNVD

Official description

An authenticated XCC user with Read-Only permission can change a different user’s password through a crafted API command. This affects ThinkSystem v2 and v3 servers with XCC; ThinkSystem v1 servers are not affected.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

How developers prevent this class of flaw

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Missing Authorization vulnerabilities (CWE-862)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Lenovo XClarity Controller (XCC)

All Lenovo XClarity Controller (XCC) vulnerabilities

Recent Missing Authorization vulnerabilities

Spotted an error? Tell us.