-
Couldn't load subscription status.
- Fork 3
[automatic] Publish 35 advisories for MbedTLS_jll #202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
GeneralMetadata has the following mbedtls versions: [MbedTLS_jll]
"2.16.0+0" = {mbedtls = "2.16.0"}
"2.16.0+1" = {mbedtls = "2.16.0"}
"2.16.0+2" = {mbedtls = "2.16.0"}
"2.16.6+0" = {mbedtls = "2.16.6"}
"2.16.6+1" = {mbedtls = "2.16.6"}
"2.16.8+0" = {mbedtls = "2.16.8"}
"2.16.8+1" = {mbedtls = "2.16.8"}
"2.24.0+0" = {mbedtls = "2.24.0"}
"2.24.0+1" = {mbedtls = "2.24.0"}
"2.24.0+2" = {mbedtls = "2.24.0"}
"2.24.0+3" = {mbedtls = "2.24.0"}
"2.24.0+4" = {mbedtls = "2.24.0"}
"2.24.0+5" = {mbedtls = "2.24.0"}
"2.25.0+0" = {mbedtls = "2.25.0"}
"2.25.0+1" = {mbedtls = "2.25.0"}
"2.25.0+2" = {mbedtls = "2.25.0"}
"2.25.0+3" = {mbedtls = "2.25.0"}
"2.26.0+0" = {mbedtls = "2.26.0"}
"2.26.0+1" = {mbedtls = "2.26.0"}
"2.26.0+2" = {mbedtls = "2.26.0"}
"2.27.0+0" = {mbedtls = "2.27.0"}
"2.27.0+1" = {mbedtls = "2.27.0"}
"2.28.0+0" = {mbedtls = "2.28.0"}
"2.28.0+1" = {mbedtls = "2.28.0"}
"2.28.0+2" = {mbedtls = "2.28.0"}
"2.28.2+0" = {mbedtls = "2.28.2"}
"2.28.2+1" = {mbedtls = "2.28.2"}
"2.28.2+2" = {mbedtls = "2.28.2"}
"2.28.6+0" = {mbedtls = "2.28.6"}
"2.28.6+1" = {mbedtls = "2.28.6"}
"2.28.6+2" = {mbedtls = "2.28.6"}
"2.28.10+0" = {mbedtls = "2.28.10"} |
as per Debian security team, this only applies if TLS 1.3 is enabled (it's not enabled)
|
This PR suggests 8 active advisories against the mbedtls JLL. Four are now corrected with my changes:
Four, however, look to be outstanding. Using their reports as those seem to have the best information here. Debian is carrying patches for 2.16 (but not 2.28). I've not found any distro that is doing such (checking Repology for other bundlers of the 2.28 line).
And while I'm looking at the mbedtls page, I can see there are a few other vulns that NVD/EUVD haven't enriched yet that affect the 2.x line:
|
This action searched
--project=mbedtls, checking 59 (+0) advisories from NVD and 1 (+8) from EUVD for advisories that pertain here. It identified 35 advisories as being related to the Julia package(s): MbedTLS_jll.7 advisories apply to all registered versions of a package
These advisories had no obvious failures but computed a range without bounds.
["*"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}arm:mbed_tlsat<= 3.0.0includes all versions["*"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}arm:mbed_tlsat< 3.1.0includes all versions["*"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}arm:mbed_tlsat< 3.5.2includes all versions["*"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}arm:mbed_tlsat< 3.6.4includes all versions["*"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}arm:mbed_tlsat< 3.6.4includes all versions["*"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}arm:mbed_tlsat< 3.6.4includes all versions["*"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}arm:mbed_tlsat< 3.6.4includes all versions1 advisories apply to the latest version of a package and do not have a patch
["< 2.27.0+0", ">= 2.28.0+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}arm:mbed_tlsat>= 2.28.0, < 3.0.0mapped to[>= 2.28.0+0], includes the latest version`27 advisories found concrete vulnerable ranges
["< 2.16.6+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.16.6+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.16.6+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.16.6+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.16.8+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.16.8+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.16.8+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.16.8+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.16.8+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.16.8+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.16.8+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.25.0+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.16.8+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.24.0+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.25.0+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.26.0+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.28.0+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}[">= 2.24.0+0, < 2.28.0+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.28.2+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.28.2+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.28.2+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.28.6+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.28.10+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.28.10+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.28.10+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}[">= 2.26.0+0, < 2.28.10+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}["< 2.28.10+0"]. Its latest version (2.28.10+0) has components: {mbedtls = "2.28.10"}