Your submission was sent successfully! Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

CVE-2023-5536

Publication date 11 December 2023

Last updated 24 July 2024


Ubuntu priority

Cvss 3 Severity Score

5.0 · Medium

Score breakdown

A feature in LXD (LP#1829071), affects the default configuration of Ubuntu Server which allows privileged users in the lxd group to escalate their privilege to root without requiring a sudo password.

Read the notes from the security team

Mitigation

Remove users from lxd group and configure multi-user LXD mode. https://discourse.ubuntu.com/t/easy-multi-user-lxd-setup/26215/4

Status

Package Ubuntu Release Status
cloud-init 23.10 mantic Ignored end of life, was ignored [mitigation must be performed manually]
23.04 lunar Ignored end of life, was ignored [mitigation must be performed manually]
22.04 LTS jammy Ignored mitigation must be performed manually
20.04 LTS focal Ignored mitigation must be performed manually
18.04 LTS bionic Ignored mitigation must be performed manually
16.04 LTS xenial Ignored mitigation must be performed manually
14.04 LTS trusty Ignored end of standard support
subiquity 23.10 mantic Not in release
23.04 lunar Not in release
22.04 LTS jammy Ignored mitigation must be performed manually
20.04 LTS focal Ignored mitigation must be performed manually
18.04 LTS bionic Ignored mitigation must be performed manually
16.04 LTS xenial Ignored end of standard support
14.04 LTS trusty Ignored end of standard support

Notes


eslerm

Ubuntu Server installed with subiquity before 23.04 is affected Ubuntu Server installed with cloud-init before 24.04 is affected Ubuntu Desktop is not affected


eslerm

a LXD feature became a vulnerability in Ubuntu Server when it was enabled as a default cloud-init and subiquity are used for tracking, these packages merely implemented Server defaults removing this LXD feature with a security patch would break existing workflows


eslerm

Mitigation must be performed manually.

Severity score breakdown

Parameter Value
Base score 5.0 · Medium
Attack vector Local
Attack complexity High
Privileges required High
User interaction Required
Scope Changed
Confidentiality High
Integrity impact None
Availability impact None
Vector CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N