Security
Headlines
HeadlinesLatestCVEs

Headline

CVE-2022-33103: [PATCH v2] fs/squashfs: sqfs_read: Prevent arbitrary code execution

Das U-Boot from v2020.10 to v2022.07-rc3 was discovered to contain an out-of-bounds write via the function sqfs_readdir().

CVE
#git

From: Miquel Raynal [email protected] To: [email protected] Cc: Thomas Petazzoni [email protected], Joao Marcos Costa [email protected], Miquel Raynal [email protected], Jincheng Wang [email protected] Subject: [PATCH v2] fs/squashfs: sqfs_read: Prevent arbitrary code execution Date: Thu, 9 Jun 2022 16:02:06 +0200 [thread overview] Message-ID: [email protected] (raw)

Following Jincheng’s report, an out-of-band write leading to arbitrary code execution is possible because on one side the squashfs logic accepts directory names up to 65535 bytes (u16), while U-Boot fs logic accepts directory names up to 255 bytes long.

Prevent such an exploit from happening by capping directory name sizes to 255. Use a define for this purpose so that developers can link the limitation to its source and eventually kill it some day by dynamically allocating this array (if ever desired).

Link: https://lore.kernel.org/all/CALO=DHFB+yBoXxVr5KcsK0iFdg+e7ywko4-e+72kjbcS8JBfPw@mail.gmail.com Reported-by: Jincheng Wang [email protected] Signed-off-by: Miquel Raynal [email protected]


Changes in v2: * Jincheng reported in private that there was a problem with small name sizes, the last byte was lost. The reason is, dirs->entry->name_size contains the length of the string minus one (and excluding the trailing ‘\0’). The previous implementation had this handled correctly but my initial fix did not kept the “+ 1” in place because it felt wrong but is actually necessary. This information is actually available in a comment a bit above in this file.

fs/squashfs/sqfs.c | 8 ++++±– include/fs.h | 4 ++± 2 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/fs/squashfs/sqfs.c b/fs/squashfs/sqfs.c index b4484fa17f5…3f1030057c4 100644 — a/fs/squashfs/sqfs.c +++ b/fs/squashfs/sqfs.c @@ -976,6 +976,7 @@ int sqfs_readdir(struct fs_dir_stream *fs_dirs, struct fs_dirent **dentp) int i_number, offset = 0, ret; struct fs_dirent *dent; unsigned char *ipos;

  • u16 name_size;

    dirs = (struct squashfs_dir_stream *)fs_dirs; if (!dirs->size) { @@ -1058,9 +1059,10 @@ int sqfs_readdir(struct fs_dir_stream *fs_dirs, struct fs_dirent **dentp) return -SQFS_STOP_READDIR; }

- /* Set entry name */

  • strncpy(dent->name, dirs->entry->name, dirs->entry->name_size + 1);
  • dent->name[dirs->entry->name_size + 1] = '\0’;
  • /* Set entry name (capped at FS_DIRENT_NAME_LEN which is a U-Boot limitation) */

  • name_size = min_t(u16, dirs->entry->name_size + 1, FS_DIRENT_NAME_LEN - 1);

  • strncpy(dent->name, dirs->entry->name, name_size);

  • dent->name[name_size] = '\0’;

    offset = dirs->entry->name_size + 1 + SQFS_ENTRY_BASE_LENGTH; dirs->entry_count–; diff --git a/include/fs.h b/include/fs.h index b43f16a692f…2195dc172ec 100644 — a/include/fs.h +++ b/include/fs.h @@ -174,6 +174,8 @@ int fs_write(const char *filename, ulong addr, loff_t offset, loff_t len, #define FS_DT_REG 8 /* regular file */ #define FS_DT_LNK 10 /* symbolic link */

+#define FS_DIRENT_NAME_LEN 256

/** * struct fs_dirent - directory entry * @@ -194,7 +196,7 @@ struct fs_dirent { /** change_time: time of last modification */ struct rtc_time change_time; /** name: file name */ - char name[256];

  • char name[FS_DIRENT_NAME_LEN]; };

/* Note: fs_dir_stream should be treated as opaque to the user of fs layer */

2.34.1

next reply other threads:[~2022-06-09 14:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-09 14:02 Miquel Raynal [this message] 2022-06-10 2:17 ` Jincheng Wang 2022-06-17 13:17 ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email using any one of the following methods:

* Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox

Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the –to, –cc, and –in-reply-to switches of git-send-email(1):

git send-email \ –[email protected] \ –[email protected] \ –[email protected] \ –[email protected] \ –[email protected] \ –[email protected] \ –subject=’Re: [PATCH v2] fs/squashfs: sqfs_read: Prevent arbitrary code execution’ \ /path/to/YOUR_REPLY

https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link

This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.

Related news

Ubuntu Security Notice USN-5764-1

Ubuntu Security Notice 5764-1 - It was discovered that U-Boot incorrectly handled certain USB DFU download setup packets. A local attacker could use this issue to cause U-Boot to crash, resulting in a denial of service, or possibly execute arbitrary code. Nicolas Bidron and Nicolas Guigo discovered that U-Boot incorrectly handled certain fragmented IP packets. A local attacker could use this issue to cause U-Boot to crash, resulting in a denial of service, or possibly execute arbitrary code. This issue only affected Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, and Ubuntu 22.04 LTS.

CVE: Latest News

CVE-2023-50976: Transactions API Authorization by oleiman · Pull Request #14969 · redpanda-data/redpanda
CVE-2023-6905
CVE-2023-6903
CVE-2023-6904
CVE-2023-3907