Bugs fixes in "snapd"
| Origin | Bug number | Title | Date fixed |
|---|---|---|---|
| CVE | CVE-2024-29069 | 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 squas | 2024-08-01 |
| CVE | CVE-2024-29068 | 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 | 2024-08-01 |
| CVE | CVE-2024-1724 | In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to the $HOME/bin path. | 2024-08-01 |
| CVE | CVE-2024-29069 | 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 squas | 2024-08-01 |
| CVE | CVE-2024-29068 | 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 | 2024-08-01 |
| CVE | CVE-2024-1724 | In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to the $HOME/bin path. | 2024-08-01 |
| CVE | CVE-2024-29069 | 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 squas | 2024-08-01 |
| CVE | CVE-2024-29068 | 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 | 2024-08-01 |
| CVE | CVE-2024-1724 | In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to the $HOME/bin path. | 2024-08-01 |
| CVE | CVE-2024-29069 | 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 squas | 2024-08-01 |
| CVE | CVE-2024-29068 | 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 | 2024-08-01 |
| CVE | CVE-2024-1724 | In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to the $HOME/bin path. | 2024-08-01 |
| CVE | CVE-2024-29069 | 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 squas | 2024-08-01 |
| CVE | CVE-2024-29068 | 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 | 2024-08-01 |
| CVE | CVE-2024-1724 | In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to the $HOME/bin path. | 2024-08-01 |
| CVE | CVE-2024-29069 | 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 squas | 2024-08-01 |
| CVE | CVE-2024-29068 | 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 | 2024-08-01 |
| CVE | CVE-2024-1724 | In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to the $HOME/bin path. | 2024-08-01 |
| CVE | CVE-2024-29069 | 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 squas | 2024-08-01 |
| CVE | CVE-2024-29068 | 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 | 2024-08-01 |
About
-
Send Feedback to @ubuntu_updates
