Overview 3,856 matches · 108 in Waratek scope · 70 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
3,856matches
108in Waratek scope2.8%
70protected1.8%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
70
1.8%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
38
1.0%
Outside Waratek scope
415
10.8%
Not applicable
3,333
86.4%
Withdrawn CVE
0
0.0%
blocked by ARMR today
70
1.8%
partly blocked
0
0.0%
not blocked
3,786
98.2%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
3,856
100.0%
split by
peak 822 / year
20041
Not applicable1
Critical1
not blocked1
No public exploit1
200515
Not applicable15
Critical1
High6
Medium6
Low2
not blocked15
No public exploit15
200621
Not applicable21
High10
Medium8
Low3
not blocked21
No public exploit21
200742
Outside Waratek scope1
Not applicable41
High20
Medium20
Low2
not blocked42
No public exploit42
200869
Outside Waratek scope1
Not applicable68
Critical3
High34
Medium30
Low2
not blocked69
No public exploit69
200944
No exploit published1
Not applicable43
High16
Medium23
Low5
not blocked44
No public exploit44
201083
Outside Waratek scope1
Not applicable82
Critical2
High30
Medium40
Low11
not blocked83
No public exploit83
201135
Not applicable35
High15
Medium18
Low2
not blocked35
No public exploit35
2012117
Protected by Waratek1
Not applicable116
High66
Medium46
Low5
blocked by ARMR today1
not blocked116
No public exploit117
2013184
Protected by Waratek2
Outside Waratek scope3
Not applicable179
Critical6
High58
Medium110
Low10
blocked by ARMR today2
not blocked182
No public exploit184
2014235
Protected by Waratek1
No exploit published2
Outside Waratek scope24
Not applicable208
Critical7
High73
Medium124
Low31
blocked by ARMR today1
not blocked234
No public exploit235
2015336
Protected by Waratek2
No exploit published3
Outside Waratek scope19
Not applicable312
Critical1
High124
Medium177
Low34
blocked by ARMR today2
not blocked334
No public exploit336
2016291
Protected by Waratek2
No exploit published9
Outside Waratek scope5
Not applicable275
Critical23
High130
Medium127
Low11
blocked by ARMR today2
not blocked289
No public exploit291
2017233
No exploit published6
Outside Waratek scope6
Not applicable221
Critical28
High86
Medium117
Low2
not blocked233
No public exploit233
2018822
Protected by Waratek25
No exploit published2
Outside Waratek scope96
Not applicable699
Critical120
High309
Medium381
Low12
blocked by ARMR today25
not blocked797
No public exploit822
2019656
Protected by Waratek15
No exploit published6
Outside Waratek scope140
Not applicable495
Critical84
High250
Medium297
Low25
blocked by ARMR today15
not blocked641
No public exploit656
2020538
Protected by Waratek22
No exploit published8
Outside Waratek scope117
Not applicable391
Critical29
High172
Medium290
Low47
blocked by ARMR today22
not blocked516
No public exploit538
202132
No exploit published1
Outside Waratek scope2
Not applicable29
High23
Medium8
Low1
not blocked32
No public exploit32
202222
Not applicable22
Critical1
High16
Medium5
not blocked22
No public exploit22
202315
Not applicable15
Critical1
High6
Medium8
not blocked15
No public exploit15
202426
Not applicable26
Critical1
High15
Medium10
not blocked26
No public exploit26
202512
Not applicable12
Critical1
High7
Medium4
not blocked12
No public exploit12
202627
Not applicable27
Critical4
High5
Medium10
Low8
not blocked27
No public exploit27
200420062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-66897 | Critical | 2026-08-24 | Not applicable | No public exploit | A path traversal vulnerability in LXD's instance template processing allows an attacker with container edit permissions, or any user launching a crafted image, to overwrite arbitrary files on the host system as root. When processing target template paths specified in metadata.yaml, LXD validates the path against a confined os.Root directory handle but subsequently opens and creates the file using os.Create with an unconfined string path. This discrepancy between path resolution checks and file creation allows an attacker to escape directory confinement, overwrite root-owned host files, and achieve host root code execution. |
| CVE-2026-63299 | Critical | 2026-08-12 | Not applicable | No public exploit | An authorization bypass vulnerability in LXD allows an authenticated user to bypass project-level disk and volume limits. Two related code paths fail to verify resource limits during volume operations: the storagePoolVolumeTypePostMove function omits the limits.AllowVolumeCreation check before moving a volume across projects, and volume snapshot restore operations skip the AllowVolumeUpdate check when the configuration is nil (Config == nil). An attacker can exploit these flaws to allocate storage resources that exceed the administrative limits configured for a project. |
| CVE-2026-62420 | Critical | 2026-08-12 | Not applicable | No public exploit | An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass target project security restrictions during cross-project instance migrations. When moving an instance cross-project to a different cluster member via POST /1.0/instances/{name} with migration: true, project: <target>, and target: <member>, the destination node skips all project restriction checks because the request arrives as an internal cluster notification. An attacker can exploit this to introduce disallowed instance configurations into a restricted project. |
| CVE-2026-28385 | Medium | 2026-06-26 | Not applicable | No public exploit | In Canonical LXD versions 4.12 through 6.9, a Server-Side Request Forgery (SSRF) vulnerability in the image import functionality allows authenticated users with the can_create_images entitlement to interact with internal network infrastructure via the /images endpoint. When importing an image from a URL source, the LXD daemon fails to validate or restrict outbound destination IP addresses, allowing connections to loopback, RFC1918 private ranges, and cloud metadata endpoints. This enables error-based port scanning and unauthorized interaction with internal HTTP services from the daemon's network position. |
| CVE-2026-49237 | High | 2026-05-28 | Not applicable | No public exploit | An issue was discovered in Canonical Multipass for macOS before version 1.16.3 due to an incomplete fix for CVE-2025-5199. While the patch in version 1.16.0 updated the ownership of the multipassd daemon binary to root:wheel, five co-located binaries (multipass, qemu-img, qemu-system-aarch64, qemu-system-x86_64, and sshfs_server) in /Library/Application Support/com.canonical.multipass/bin/ retain ownership by the installing user and remain writable. Because the root LaunchDaemon (com.canonical.multipassd.plist) configures a PATH environment variable that prioritizes this user-writable directory and invokes these auxiliary binaries by their bare names, a local attacker can replace an auxiliary binary (such as qemu-img) with a malicious wrapper. When the root daemon subsequently triggers the binary during routine execution (e.g., via multipass launch), the malicious code executes with root privileges, leading to local privilege escalation. |
| CVE-2026-47337 | Low | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain SAUCE patches with a possible NULL pointer dereference in the handling of AF_INET/AF_INET6 socket mediation. The bug can be triggered by an unprivileged local user. This can lead to a kernel oops. |
| CVE-2026-47336 | Low | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8 contains SAUCE patches with a possible use of an uninitialized variable in AppArmor AF_INET/AF_INET6 socket mediation code. The bug can be triggered by an unprivileged local user and could result in incorrect fine-grained mediation of network sockets. |
| CVE-2026-47335 | Medium | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8 contains SAUCE patches with a possible NULL pointer dereference in the handling of AppArmor notifications. The bug can be triggered by an unprivileged local user. This can lead to a kernel panic. |
| CVE-2026-47334 | Medium | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain AppArmor SAUCE patches which incorrectly sleep while holding a spinlock in notification handling code. The bug can be triggered by an unprivileged local user and can result in kernel panic or deadlock. |
| CVE-2026-47333 | High | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain AppArmor SAUCE patches which can potentially incorrectly compute the size of an internal buffer, leading to a heap memory out-of-bounds read in notification handling code. The bug can be triggered by an unprivileged local user and can result in invalid data being processed by the AppArmor DFA policy engine. |
| CVE-2026-47332 | Medium | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain AppArmor SAUCE patches which incorrectly validate the size of an internal structure, leading to an out-of-bounds read in notification handling code. The bug can be triggered by an unprivileged local user and can result in information disclosure from adjacent slab objects. |
| CVE-2026-47331 | High | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8 contains AppArmor SAUCE patches which fail to acquire a lock when modifying a linked list. An unprivileged local user could trigger the race condition that can lead to a use-after-free (UAF) and, theoretically, arbitrary code execution. |
| CVE-2026-47330 | Low | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 7.17 and 7.0 contain AppArmor SAUCE patches which can, under certain circumstances, use an uninitialized variable in notification handling code. The bug can be triggered by an unprivileged local user and can result in the incorrect caching of AppArmor notification responses. |
| CVE-2026-47329 | Low | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain SAUCE patches which fail to validate invalid sizes of the name field in AppAmor notification responses. The bug can be triggered by an unprivileged local user and could result in handling of crafted responses. |
| CVE-2026-47328 | Medium | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain AppArmor SAUCE patches which incorrectly attempt to free a pointer which was not previously kmalloc()d, while at the same time leaking allocated memory. The bug can be triggered by an unprivileged local user and can result in the corruption of slab metadata and could lead to resource exhaustion. |
| CVE-2026-47327 | Low | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain SAUCE patches with a possible NULL pointer dereference in the handling of AppArmor notifications. The bug can be triggered by an unprivileged local user. This can lead to a kernel oops. |
| CVE-2026-47326 | Medium | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain SAUCE patches with a memory leak in the handling of big responses to AppArmor notifications. The bug can be triggered by an unprivileged local user. The memory leak could lead to resource exhaustion. |
| CVE-2026-6369 | Medium | 2026-04-20 | Not applicable | No public exploit | An improper access control vulnerability in the canonical-livepatch snap client prior to version 10.15.0 allows a local unprivileged user to obtain a sensitive, root-level authentication token by sending an unauthenticated request to the livepatchd.sock Unix domain socket. This vulnerability is exploitable on systems where an administrator has already enabled the Livepatch client with a valid Ubuntu Pro subscription. This token allows an attacker to access Livepatch services using the victim's credentials, as well as potentially cause issues to the Livepatch server. |
| CVE-2026-5412 | Critical | 2026-04-10 | Not applicable | No public exploit | In Juju versions prior to 2.9.57 and 3.6.21, an authorization issue exists in the Controller facade. An authenticated user can call the CloudSpec API method to extract the cloud credentials used to bootstrap the controller. This allows a low-privileged user to access sensitive credentials. This issue is resolved in Juju versions 2.9.57 and 3.6.21. |
| CVE-2025-15480 | Low | 2026-04-09 | Not applicable | No public exploit | In Ubuntu, ubuntu-desktop-provision version 24.04.4 could leak sensitive user credentials during crash reporting. Upon installation failure, if a user submitted a bug report to Launchpad, ubuntu-desktop-provision could include the user's password hash in the attached logs. |
| CVE-2025-14551 | Low | 2026-04-09 | Not applicable | No public exploit | In Ubuntu, Subiquity version 24.04.4 could leak sensitive user credentials during crash reporting. Upon installation failure, if a user submitted a bug report to Launchpad, Subiquity could include certain user credentials, such as the user's plaintext Wi-Fi password, in the attached logs. |
| CVE-2025-68152 | Medium | 2026-04-03 | Not applicable | No public exploit | Juju is an open source application orchestration engine that enables any application operation on any infrastructure at any scale through special operators called ‘charms’. From versions 2.9 to before 2.9.56 and 3.6 to before 3.6.19, it is possible that a compromised workload machine under a Juju controller can read any log file for any entity in any model at any level. This issue has been patched in versions 2.9.56 and 3.6.19. |
| CVE-2026-32693 | High | 2026-03-18 | Not applicable | No public exploit | In Juju from version 3.0.0 through 3.6.18, the authorization of the "secret-set" tool is not performed correctly, which allows a grantee to update the secret content, and can lead to reading or updating other secrets. When the "secret-set" tool logs an error in an exploitation attempt, the secret is still updated contrary to expectations, and the new value is visible to both the owner and the grantee. |
| CVE-2026-32692 | High | 2026-03-18 | Not applicable | No public exploit | An authorization bypass vulnerability in the Vault secrets back-end implementation of Juju versions 3.1.6 through 3.6.18 allows an authenticated unit agent to perform unauthorized updates to secret revisions. With sufficient information, an attacker can poison any existing secret revision within the scope of that Vault secret back-end. |
| CVE-2026-32691 | Medium | 2026-03-18 | Not applicable | No public exploit | A race condition in the secrets management subsystem of Juju versions 3.0.0 through 3.6.18 allows an authenticated unit agent to claim ownership of a newly initialized secret. Between generating a Juju Secret ID and creating the secret's first revision, an attacker authenticated as another unit agent can claim ownership of a known secret. This leads to the attacking unit being able to read the content of the initial secret revision. |
| CVE-2026-3497 | Medium | 2026-03-12 | Not applicable | No public exploit | Vulnerability in the OpenSSH GSSAPI delta included in various Linux distributions. This vulnerability affects the GSSAPI patches added by various Linux distributions and does not affect the OpenSSH upstream project itself. The usage of sshpkt_disconnect() on an error, which does not terminate the process, allows an attacker to send an unexpected GSSAPI message type during the GSSAPI key exchange to the server, which will call the underlying function and continue the execution of the program without setting the related connection variables. As the variables are not initialized to NULL the code later accesses those uninitialized variables, accessing random memory, which could lead to undefined behavior. The recommended workaround is to use ssh_packet_disconnect() instead, which does terminate the process. The impact of the vulnerability depends heavily on the compiler flag hardening configuration. |
| CVE-2026-3351 | Low | 2026-03-03 | Not applicable | No public exploit | Improper authorization in the API endpoint GET /1.0/certificates in Canonical LXD 6.6 on Linux allows an authenticated, restricted user to enumerate all certificate fingerprints trusted by the lxd server. |
| CVE-2025-7044 | High | 2025-12-03 | Not applicable | No public exploit | An Improper Input Validation vulnerability exists in the user websocket handler of MAAS. An authenticated, unprivileged attacker can intercept a user.update websocket request and inject the is_superuser property set to true. The server improperly validates this input, allowing the attacker to self-promote to an administrator role. This results in full administrative control over the MAAS deployment. |
| CVE-2025-54289 | High | 2025-10-02 | Not applicable | No public exploit | Privilege Escalation in operations API in Canonical LXD <6.5 on multiple platforms allows attacker with read permissions to hijack terminal or console sessions and execute arbitrary commands via WebSocket connection hijacking format |
| CVE-2025-54286 | High | 2025-10-02 | Not applicable | No public exploit | Cross-Site Request Forgery (CSRF) in LXD-UI in Canonical LXD versions >= 5.0 on Linux allows an attacker to create and start container instances without user consent via crafted HTML form submissions exploiting client certificate authentication. |
| CVE-2024-6174 | High | 2025-06-26 | Not applicable | No public exploit | When a non-x86 platform is detected, cloud-init grants root access to a hardcoded url with a local IP address. To prevent this, cloud-init default configurations disable platform enumeration. |
| CVE-2024-11584 | Medium | 2025-06-26 | Not applicable | No public exploit | cloud-init through 25.1.2 includes the systemd socket unit cloud-init-hotplugd.socket with default SocketMode that grants 0666 permissions, making it world-writable. This is used for the "/run/cloud-init/hook-hotplug-cmd" FIFO. An unprivileged user could trigger hotplug-hook commands. |
| CVE-2025-5689 | High | 2025-06-16 | Not applicable | No public exploit | A flaw was found in the temporary user record that authd uses in the pre-auth NSS. As a result, a user login for the first time will be considered to be part of the root group in the context of that SSH session. |
| CVE-2023-5616 | Medium | 2025-04-15 | Not applicable | No public exploit | In Ubuntu, gnome-control-center did not properly reflect SSH remote login status when the system was configured to use systemd socket activation for openssh-server. This could unknowingly leave the local machine exposed to remote SSH access contrary to expectation of the user. |
| CVE-2023-0881 | High | 2025-03-31 | Not applicable | No public exploit | Running DDoS on tcp port 22 will trigger a kernel crash. This issue is introduced by the backport of a commit regarding nft_lookup without the subsequent fixes that were introduced after this commit. The resolution of this CVE introduces those commits to the linux-bluefield package. |
| CVE-2022-1804 | Medium | 2025-03-25 | Not applicable | No public exploit | accountsservice no longer drops permissions when writting .pam_environment |
| CVE-2023-0092 | Medium | 2025-01-31 | Not applicable | No public exploit | An authenticated user who has read access to the juju controller model, may construct a remote request to download an arbitrary file from the controller's filesystem. |
| CVE-2022-28653 | High | 2025-01-31 | Not applicable | No public exploit | Users can consume unlimited disk space in /var/crash |
| CVE-2022-1736 | Critical | 2025-01-31 | Not applicable | No public exploit | Ubuntu's configuration of gnome-control-center allowed Remote Desktop Sharing to be enabled by default. |
| CVE-2024-9312 | High | 2024-10-10 | Not applicable | No public exploit | Authd, through version 0.3.6, did not sufficiently randomize user IDs to prevent collisions. A local attacker who can register user names could spoof another user's ID and gain their privileges. |
| CVE-2024-9313 | High | 2024-10-03 | Not applicable | No public exploit | Authd PAM module before version 0.3.5 can allow broker-managed users to impersonate any other user managed by the same broker and perform any PAM operation with it, including authenticating as them. |
| CVE-2024-8038 | High | 2024-10-02 | Not applicable | No public exploit | Vulnerable juju introspection abstract UNIX domain socket. An abstract UNIX domain socket responsible for introspection is available without authentication locally to network namespace users. This enables denial of service attacks. |
| CVE-2024-8037 | Medium | 2024-10-02 | Not applicable | No public exploit | Vulnerable juju hook tool abstract UNIX domain socket. When combined with an attack of JUJU_CONTEXT_ID, any user on the local system with access to the default network namespace may connect to the @/var/lib/juju/agents/unit-xxxx-yyyy/agent.socket and perform actions that are normally reserved to a juju charm. |
| CVE-2024-7558 | High | 2024-10-02 | Not applicable | No public exploit | JUJU_CONTEXT_ID is a predictable authentication secret. On a Juju machine (non-Kubernetes) or Juju charm container (on Kubernetes), an unprivileged user in the same network namespace can connect to an abstract domain socket and guess the JUJU_CONTEXT_ID value. This gives the unprivileged user access to the same information and tools as the Juju charm. |
| CVE-2024-8287 | High | 2024-09-18 | Not applicable | No public exploit | Anbox Management Service, in versions 1.17.0 through 1.23.0, does not validate the TLS certificate provided to it by the Anbox Stream Agent. An attacker must be able to machine-in-the-middle the Anbox Stream Agent from within an internal network before they can attempt to take advantage of this. |
| CVE-2024-6984 | High | 2024-07-29 | Not applicable | No public exploit | An issue was discovered in Juju that resulted in the leak of the sensitive context ID, which allows a local unprivileged attacker to access other sensitive data or relation accessible to the local charm. |
| CVE-2024-29069 | High | 2024-07-25 | Not applicable | No public exploit | In snapd versions prior to 2.62, snapd failed to properly check the destination of symbolic links when extracting a snap. The snap format is a squashfs file-system image and so can contain symbolic links and other file types. Various file entries within the snap squashfs image (such as icons and desktop files etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained symbolic links at these paths could then cause snapd to write out the contents of the symbolic link destination into a world-readable directory. This in-turn could allow an unprivileged user to gain access to privileged information. |
| CVE-2024-29068 | Medium | 2024-07-25 | Not applicable | No public exploit | In snapd versions prior to 2.62, snapd failed to properly check the file type when extracting a snap. The snap format is a squashfs file-system image and so can contain files that are non-regular files (such as pipes or sockets etc). Various file entries within the snap squashfs image (such as icons etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained non-regular files at these paths could then cause snapd to block indefinitely trying to read from such files and cause a denial of service. |
| CVE-2024-6714 | High | 2024-07-23 | Not applicable | No public exploit | An issue was discovered in provd before version 0.1.5 with a setuid binary, which allows a local attacker to escalate their privilege. |
| CVE-2020-27352 | Critical | 2024-06-21 | Not applicable | No public exploit | When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify Delegate=yes - as a result systemd will move processes from the containers created and managed by these snaps into the cgroup of the main daemon within the snap itself when reloading system units. This may grant additional privileges to a container within the snap that were not originally intended. |
| CVE-2022-4968 | Medium | 2024-06-07 | Not applicable | No public exploit | netplan leaks the private key of wireguard to local users. Versions after 1.0 are not affected. |
| CVE-2022-28658 | Medium | 2024-06-04 | Not applicable | No public exploit | Apport argument parsing mishandles filename splitting on older kernels resulting in argument spoofing |
| CVE-2022-28657 | High | 2024-06-04 | Not applicable | No public exploit | Apport does not disable python crash handler before entering chroot |
| CVE-2022-28656 | Medium | 2024-06-04 | Not applicable | No public exploit | is_closing_session() allows users to consume RAM in the Apport process |
| CVE-2022-28655 | High | 2024-06-04 | Not applicable | No public exploit | is_closing_session() allows users to create arbitrary tcp dbus connections |
| CVE-2022-28654 | Medium | 2024-06-04 | Not applicable | No public exploit | is_closing_session() allows users to fill up apport.log |
| CVE-2022-28652 | Medium | 2024-06-04 | Not applicable | No public exploit | ~/.config/apport/settings parsing is vulnerable to "billion laughs" attack |
| CVE-2022-1242 | High | 2024-06-03 | Not applicable | No public exploit | Apport can be tricked into connecting to arbitrary sockets as the root user |
| CVE-2021-3899 | High | 2024-06-03 | Not applicable | No public exploit | There is a race condition in the 'replaced executable' detection that, with the correct local configuration, allow an attacker to execute arbitrary code as root. |
| CVE-2024-3250 | Medium | 2024-04-04 | Not applicable | No public exploit | It was discovered that Canonical's Pebble service manager read-file API and the associated pebble pull command, before v1.10.2, allowed unprivileged local users to read files with root-equivalent permissions when Pebble was running as root. Fixes are also available as backports to v1.1.1, v1.4.2, and v1.7.4. |
| CVE-2023-49721 | Medium | 2024-02-14 | Not applicable | No public exploit | An insecure default to allow UEFI Shell in EDK2 was left enabled in LXD. This allows an OS-resident attacker to bypass Secure Boot. |
| CVE-2023-1032 | Medium | 2024-01-08 | Not applicable | No public exploit | The Linux kernel io_uring IORING_OP_SOCKET operation contained a double free in function __sys_socket_file() in file net/socket.c. This issue was introduced in da214a475f8bd1d3e9e7a19ddfeb4d1617551bab and fixed in 649c15c7691e9b13cbe9bf6c65c365350e056067. |
| CVE-2022-3328 | High | 2024-01-08 | Not applicable | No public exploit | Race condition in snap-confine's must_mkdir_and_open_with_perms() |
| CVE-2022-2585 | High | 2024-01-08 | Not applicable | No public exploit | It was discovered that when exec'ing from a non-leader thread, armed POSIX CPU timers would be left on a list but freed, leading to a use-after-free. |
| CVE-2021-3600 | High | 2024-01-08 | Not applicable | No public exploit | It was discovered that the eBPF implementation in the Linux kernel did not properly track bounds information for 32 bit registers when performing div and mod operations. A local attacker could use this to possibly execute arbitrary code. |
| CVE-2023-5536 | Medium | 2023-12-12 | Not applicable | No public exploit | 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. |
| CVE-2023-5182 | Medium | 2023-10-07 | Not applicable | No public exploit | Sensitive data could be exposed in logs of subiquity version 23.09.1 and earlier. An attacker in the adm group could use this information to find hashed passwords and possibly escalate their privilege. |
| CVE-2023-3777 | High | 2023-09-06 | Not applicable | No public exploit | A use-after-free vulnerability in the Linux kernel's netfilter: nf_tables component can be exploited to achieve local privilege escalation. When nf_tables_delrule() is flushing table rules, it is not checked whether the chain is bound and the chain's owner rule can also release the objects in certain circumstances. We recommend upgrading past commit 6eaf41e87a223ae6f8e7a28d6e78384ad7e407f8. |
| CVE-2023-40283 | High | 2023-08-14 | Not applicable | No public exploit | An issue was discovered in l2cap_sock_release in net/bluetooth/l2cap_sock.c in the Linux kernel before 6.4.10. There is a use-after-free because the children of an sk are mishandled. |
| CVE-2023-3567 | High | 2023-07-24 | Not applicable | No public exploit | A use-after-free flaw was found in vcs_read in drivers/tty/vt/vc_screen.c in vc_screen in the Linux Kernel. This issue may allow an attacker with local user access to cause a system crash or leak internal kernel information. |
| CVE-2023-3389 | High | 2023-06-28 | Not applicable | No public exploit | A use-after-free vulnerability in the Linux Kernel io_uring subsystem can be exploited to achieve local privilege escalation. Racing a io_uring cancel poll request with a linked timeout can cause a UAF in a hrtimer. We recommend upgrading past commit ef7dfac51d8ed961b742218f526bd589f3900a59 (4716c73b188566865bdd79c3a6709696a224ac04 for 5.10 stable and 0e388fce7aec40992eadee654193cad345d62663 for 5.15 stable). |
| CVE-2023-32551 | Medium | 2023-06-06 | Not applicable | No public exploit | Landscape allowed URLs which caused open redirection. |
| CVE-2023-32550 | Critical | 2023-06-06 | Not applicable | No public exploit | Landscape's server-status page exposed sensitive system information. This data leak included GET requests which contain information to attack and leak further information from the Landscape API. |
| CVE-2023-32549 | High | 2023-06-06 | Not applicable | No public exploit | Landscape cryptographic keys were insecurely generated with a weak pseudo-random generator. |
| CVE-2023-2612 | Medium | 2023-05-31 | Not applicable | No public exploit | Jean-Baptiste Cayrou discovered that the shiftfs file system in the Ubuntu Linux kernel contained a race condition when handling inode locking in some situations. A local attacker could use this to cause a denial of service (kernel deadlock). |
| CVE-2023-1786 | Medium | 2023-04-26 | Not applicable | No public exploit | Sensitive data could be exposed in logs of cloud-init before version 23.1.2. An attacker could use this information to find hashed passwords and possibly escalate their privilege. |
| CVE-2022-2084 | Medium | 2023-04-19 | Not applicable | No public exploit | Sensitive data could be exposed in world readable logs of cloud-init before version 22.3 when schema failures are reported. This leak could include hashed passwords. |
| CVE-2021-3429 | Medium | 2023-04-19 | Not applicable | No public exploit | When instructing cloud-init to set a random password for a new user account, versions before 21.2 would write that password to the world-readable log file /var/log/cloud-init-output.log. This could allow a local user to log in as another user. |
| CVE-2020-11935 | Medium | 2023-04-07 | Not applicable | No public exploit | It was discovered that aufs improperly managed inode reference counts in the vfsub_dentry_open() method. A local attacker could use this vulnerability to cause a denial of service attack. |
| CVE-2023-1380 | High | 2023-03-27 | Not applicable | No public exploit | A slab-out-of-bound read problem was found in brcmf_get_assoc_ies in drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c in the Linux Kernel. This issue could occur when assoc_info->req_len data is bigger than the size of the buffer, defined as WL_EXTRA_BUF_MAX, leading to a denial of service. |
| CVE-2022-40617 | High | 2022-10-31 | Not applicable | No public exploit | strongSwan before 5.9.8 allows remote attackers to cause a denial of service in the revocation plugin by sending a crafted end-entity (and intermediate CA) certificate that contains a CRL/OCSP URL that points to a server (under the attacker's control) that doesn't properly respond but (for example) just does nothing after the initial TCP handshake, or sends an excessive amount of application data. |
| CVE-2022-39177 | High | 2022-09-02 | Not applicable | No public exploit | BlueZ before 5.59 allows physically proximate attackers to cause a denial of service because malformed and invalid capabilities can be processed in profiles/audio/avdtp.c. |
| CVE-2022-39176 | High | 2022-09-02 | Not applicable | No public exploit | BlueZ before 5.59 allows physically proximate attackers to obtain sensitive information because profiles/audio/avrcp.c does not validate params_len. |
| CVE-2022-1184 | Medium | 2022-08-29 | Not applicable | No public exploit | A use-after-free flaw was found in fs/ext4/namei.c:dx_insert_block() in the Linux kernel’s filesystem sub-component. This flaw allows a local attacker with a user privilege to cause a denial of service. |
| CVE-2021-3975 | Medium | 2022-08-23 | Not applicable | No public exploit | A use-after-free flaw was found in libvirt. The qemuMonitorUnregister() function in qemuProcessHandleMonitorEOF is called using multiple threads without being adequately protected by a monitor lock. This flaw could be triggered by the virConnectGetAllDomainStats API when the guest is shutting down. An unprivileged client with a read-only connection could use this flaw to perform a denial of service attack by causing the libvirt daemon to crash. |
| CVE-2021-3905 | High | 2022-08-23 | Not applicable | No public exploit | A memory leak was found in Open vSwitch (OVS) during userspace IP fragmentation processing. An attacker could use this flaw to potentially exhaust available memory by keeping sending packet fragments. |
| CVE-2021-3748 | High | 2022-03-23 | Not applicable | No public exploit | A use-after-free vulnerability was found in the virtio-net device of QEMU. It could occur when the descriptor's address belongs to the non direct access region, due to num_buffers being set after the virtqueue elem has been unmapped. A malicious guest could use this flaw to crash QEMU, resulting in a denial of service condition, or potentially execute code on the host with the privileges of the QEMU process. |
| CVE-2021-3737 | High | 2022-03-04 | Not applicable | No public exploit | A flaw was found in python. An improperly handled HTTP response in the HTTP client code of python may allow a remote attacker, who controls the HTTP server, to make the client script enter an infinite loop, consuming CPU time. The highest threat from this vulnerability is to system availability. |
| CVE-2021-3640 | High | 2022-03-03 | Not applicable | No public exploit | A flaw use-after-free in function sco_sock_sendmsg() of the Linux kernel HCI subsystem was found in the way user calls ioct UFFDIO_REGISTER or other way triggers race condition of the call sco_conn_del() together with the call sco_sock_sendmsg() with the expected controllable faulting memory page. A privileged local user could use this flaw to crash the system or escalate their privileges on the system. |
| CVE-2021-4115 | Medium | 2022-02-21 | Not applicable | No public exploit | There is a flaw in polkit which can allow an unprivileged user to cause polkit to crash, due to process file descriptor exhaustion. The highest threat from this vulnerability is to availability. NOTE: Polkit process outage duration is tied to the failing process being reaped and a new one being spawned |
| CVE-2021-4093 | High | 2022-02-18 | Not applicable | No public exploit | A flaw was found in the KVM's AMD code for supporting the Secure Encrypted Virtualization-Encrypted State (SEV-ES). A KVM guest using SEV-ES can trigger out-of-bounds reads and writes in the host kernel via a malicious VMGEXIT for a string I/O instruction (for example, outs or ins) using the exit reason SVM_EXIT_IOIO. This issue results in a crash of the entire system or a potential guest-to-host escape scenario. |
| CVE-2020-25722 | High | 2022-02-18 | Not applicable | No public exploit | Multiple flaws were found in the way samba AD DC implemented access and conformance checking of stored data. An attacker could use this flaw to cause total domain compromise. |
| CVE-2020-25719 | High | 2022-02-18 | Not applicable | No public exploit | A flaw was found in the way Samba, as an Active Directory Domain Controller, implemented Kerberos name-based authentication. The Samba AD DC, could become confused about the user a ticket represents if it did not strictly require a Kerberos PAC and always use the SIDs found within. The result could include total domain compromise. |
| CVE-2020-25717 | High | 2022-02-18 | Not applicable | No public exploit | A flaw was found in the way Samba maps domain users to local users. An authenticated attacker could use this flaw to cause possible privilege escalation. |
| CVE-2016-2124 | Medium | 2022-02-18 | Not applicable | No public exploit | A flaw was found in the way samba implemented SMB1 authentication. An attacker could use this flaw to retrieve the plaintext password sent over the wire even if Kerberos authentication was required. |
| CVE-2021-44731 | High | 2022-02-17 | Not applicable | No public exploit | A race condition existed in the snapd 2.54.2 snap-confine binary when preparing a private mount namespace for a snap. This could allow a local attacker to gain root privileges by bind-mounting their own contents inside the snap's private mount namespace and causing snap-confine to execute arbitrary code and hence gain privilege escalation. Fixed in snapd versions 2.54.3+18.04, 2.54.3+20.04 and 2.54.3+21.10.1 |
| CVE-2021-44730 | High | 2022-02-17 | Not applicable | No public exploit | snapd 2.54.2 did not properly validate the location of the snap-confine binary. A local attacker who can hardlink this binary to another location to cause snap-confine to execute other arbitrary binaries and hence gain privilege escalation. Fixed in snapd versions 2.54.3+18.04, 2.54.3+20.04 and 2.54.3+21.10.1 |
| CVE-2021-4120 | High | 2022-02-17 | Not applicable | No public exploit | snapd 2.54.2 fails to perform sufficient validation of snap content interface and layout paths, resulting in the ability for snaps to inject arbitrary AppArmor policy rules via malformed content interface and layout declarations and hence escape strict snap confinement. Fixed in snapd versions 2.54.3+18.04, 2.54.3+20.04 and 2.54.3+21.10.1 |
| CVE-2021-3155 | Medium | 2022-02-17 | Not applicable | No public exploit | snapd 2.54.2 and earlier created ~/snap directories in user home directories without specifying owner-only permissions. This could allow a local attacker to read information that should have been private. Fixed in snapd versions 2.54.3+18.04, 2.54.3+20.04 and 2.54.3+21.10.1 |
| CVE-2021-45079 | Critical | 2022-01-31 | Not applicable | No public exploit | In strongSwan before 5.9.5, a malicious responder can send an EAP-Success message too early without actually authenticating the client and (in the case of EAP methods with mutual authentication and EAP-only authentication for IKEv2) even without server authentication. |