[mbedtls] New version v2.28.1010: upstream 2.28.10 + Debian's (2.16.9) security patches#12380
Conversation
extracted from [libmbedtls-dev (2.16.9-0.1+deb11u3) [security]](https://packages.debian.org/bullseye/libmbedtls-dev)
06-CVE-2025-48965-0-1.patch is a no-op
07-CVE-2025-48965-0-2.patch adds a test case as it already existed; my first attempt here simply duplicated the definition
|
OK, still outstanding are last week's CVE-2025-54764 and CVE-2025-59438. There are suggested commits for backports there, but I'm guessing those will be more challenging. |
|
Is this good to go now? |
|
Let’s give it a bit here. I’d value any extra eyes on the diff^2s, and I’m gonna give a shot at backports for those other two issues. |
|
You will probably need to tag someone in particular if you'd like additional review - there don't tend to be a lot of casual eyes combing Yggdrasil (except our beloved @giordano ) |
|
OK, I tried a few different ways to cherry-pick the patches for CVE-2025-54764 and CVE-2025-59438, but they are highly challenging. I've not seen any other ecosystem successfully backport those to v2.x, nor has anyone else pitched in on their mailing-list. Let's not let these hold up the other fixes. I've also re-reviewed the diff² here and am pretty happy with the state of this PR. Shall we merge this? |
…60744) This PR bumps MbedTLS on Julia 1.10 to [2.28.1010](JuliaPackaging/Yggdrasil#12380), which is upstream 2.28.10 plus Debian's (2.16.9) security patches. ### Check list (from the [devdocs](https://docs.julialang.org/en/v1.12/devdocs/build/build/#Update-the-version-number-of-a-dependency)) Version numbers: - [x] `deps/$(libname).version`: `LIBNAME_VER`, `LIBNAME_BRANCH`, `LIBNAME_SHA1` and `LIBNAME_JLL_VER` - [x] `stdlib/$(LIBNAME_JLL_NAME)_jll/Project.toml`: `version` Checksum: - [x] `deps/checksums/$(libname)` - [ ] `deps/checksums/$(LIBNAME_JLL_NAME)-*/`: `md5` and `sha512` - I don't think this file exists anymore. It looks like the checksums have been combined into `deps/checksums/mbedtls`. Patches: - [x] `deps/$(libname).mk` - [x] `deps/patches/$(libname)-*.patch` --------- Co-authored-by: Andy Dienes <51664769+adienes@users.noreply.github.com> Co-authored-by: Ian Butterworth <i.r.butterworth@gmail.com> Co-authored-by: Kristoffer Carlsson <kcarlsson89@gmail.com> Co-authored-by: KristofferC <kristoffer.carlsson@juliacomputing.com> Co-authored-by: Max Horn <max@quendi.de> Co-authored-by: Milan Bouchet-Valat <nalimilan@club.fr> Co-authored-by: Eddie Groshev <eddie_g_89@hotmail.com> Co-authored-by: Jameson Nash <vtjnash@gmail.com> Co-authored-by: Valentin Churavy <v.churavy@gmail.com> Co-authored-by: Jeff Bezanson <jeff.bezanson@gmail.com> Co-authored-by: Mosè Giordano <765740+giordano@users.noreply.github.com> Co-authored-by: Em Chu <61633163+mlechu@users.noreply.github.com> Co-authored-by: Michiel Dral <m.c.dral@gmail.com> Co-authored-by: Erik Schnetter <schnetter@gmail.com>
…60744) This PR bumps MbedTLS on Julia 1.10 to [2.28.1010](JuliaPackaging/Yggdrasil#12380), which is upstream 2.28.10 plus Debian's (2.16.9) security patches. [devdocs](https://docs.julialang.org/en/v1.12/devdocs/build/build/#Update-the-version-number-of-a-dependency)) Version numbers: - [x] `deps/$(libname).version`: `LIBNAME_VER`, `LIBNAME_BRANCH`, `LIBNAME_SHA1` and `LIBNAME_JLL_VER` - [x] `stdlib/$(LIBNAME_JLL_NAME)_jll/Project.toml`: `version` Checksum: - [x] `deps/checksums/$(libname)` - [ ] `deps/checksums/$(LIBNAME_JLL_NAME)-*/`: `md5` and `sha512` - I don't think this file exists anymore. It looks like the checksums have been combined into `deps/checksums/mbedtls`. Patches: - [x] `deps/$(libname).mk` - [x] `deps/patches/$(libname)-*.patch` --------- Co-authored-by: Andy Dienes <51664769+adienes@users.noreply.github.com> Co-authored-by: Ian Butterworth <i.r.butterworth@gmail.com> Co-authored-by: Kristoffer Carlsson <kcarlsson89@gmail.com> Co-authored-by: KristofferC <kristoffer.carlsson@juliacomputing.com> Co-authored-by: Max Horn <max@quendi.de> Co-authored-by: Milan Bouchet-Valat <nalimilan@club.fr> Co-authored-by: Eddie Groshev <eddie_g_89@hotmail.com> Co-authored-by: Jameson Nash <vtjnash@gmail.com> Co-authored-by: Valentin Churavy <v.churavy@gmail.com> Co-authored-by: Jeff Bezanson <jeff.bezanson@gmail.com> Co-authored-by: Mosè Giordano <765740+giordano@users.noreply.github.com> Co-authored-by: Em Chu <61633163+mlechu@users.noreply.github.com> Co-authored-by: Michiel Dral <m.c.dral@gmail.com> Co-authored-by: Erik Schnetter <schnetter@gmail.com>

The goal here is to address the CVEs: CVE-2025-47917, CVE-2025-48965, CVE-2025-52496, and CVE-2025-52497.
The most important diff to review is the re-landing of the patches to v2.28.10. These ranged in difficulty to an automatic three-way merge to completely manual re-implementation. That's 5f20384.
My process here was the fairly simple: