Microsoft security update for CVE-2024-51744
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-51744. This page also shows what EchelonGraph holds for CVE-2024-51744, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products69
- azl3 application-gateway-kubernetes-ingress 1.7.2-3 on Azure Linux 3.0
- azl3 application-gateway-kubernetes-ingress 1.7.7-1 on Azure Linux 3.0
- azl3 azcopy 10.25.1-4 on Azure Linux 3.0
- azl3 cert-manager 1.12.13-2 on Azure Linux 3.0
- azl3 cert-manager 1.12.15-1 on Azure Linux 3.0
- azl3 coredns 1.11.1-4 on Azure Linux 3.0
- azl3 coredns 1.11.4-1 on Azure Linux 3.0
- azl3 dcos-cli 1.2.0-18 on Azure Linux 3.0
- azl3 etcd 3.5.12-2 on Azure Linux 3.0
- azl3 etcd 3.5.18-1 on Azure Linux 3.0
- azl3 flannel 0.24.2-13 on Azure Linux 3.0
- azl3 flannel 0.24.2-14 on Azure Linux 3.0
- azl3 influxdb 2.7.5-3 on Azure Linux 3.0
- azl3 influxdb 2.7.5-5 on Azure Linux 3.0
- azl3 jx 3.10.116-2 on Azure Linux 3.0
- azl3 jx 3.10.182-1 on Azure Linux 3.0
- azl3 keda 2.14.1-6 on Azure Linux 3.0
- azl3 keda 2.14.1-7 on Azure Linux 3.0
- azl3 kubernetes 1.30.10-5 on Azure Linux 3.0
- azl3 kubernetes 1.30.10-7 on Azure Linux 3.0
- azl3 moby-engine 25.0.3-13 on Azure Linux 3.0
- azl3 packer 1.9.5-8 on Azure Linux 3.0
- azl3 packer 1.9.5-9 on Azure Linux 3.0
- azl3 prometheus 2.45.4-12 on Azure Linux 3.0
- azl3 telegraf 1.31.0-10 on Azure Linux 3.0
- azl3 telegraf 1.31.0-6 on Azure Linux 3.0
- cbl2 application-gateway-kubernetes-ingress 1.4.0-25 on CBL Mariner 2.0
- cbl2 application-gateway-kubernetes-ingress 1.4.0-25 on CBL-Mariner 2.0
- cbl2 azcopy 10.25.1-4 on CBL Mariner 2.0
- cbl2 azcopy 10.25.1-5 on CBL Mariner 2.0
- +39 more not shown
✅ Updates Microsoft lists: 32 updates
32 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 1.29.4-14 |
| — | Security Update | 0.59.0-27 |
| — | Security Update | 10.25.1-4 |
| — | Security Update | 1.4.0-25 |
| — | Security Update | 3.5.21-1 |
| — | Security Update | 1.9.5-11 |
| — | Security Update | 3.5.18-1 |
| — | Security Update | 3.10.182-1 |
| — | Security Update | 2.45.4-12 |
| — | Security Update | 1.31.0-6 |
| — | Security Update | 1.30.10-5 |
| — | Security Update | 2.14.1-6 |
| — | Security Update | 1.2.0-18 |
| — | Security Update | 1.7.7-1 |
| — | Security Update | 2.7.5-3 |
| — | Security Update | 1.9.5-8 |
| — | Security Update | 0.24.2-13 |
| — | Security Update | 1.12.15-1 |
| — | Security Update | 1.11.4-1 |
| — | Security Update | 25.0.3-13 |
| — | Security Update | 24.0.9-17 |
| — | Security Update | 2.6.1-22 |
| — | Security Update | 0.0.2-22 |
| — | Security Update | 1.11.1-18 |
| — | Security Update | 2.4.0-29 |
| — | Security Update | 1.28.4-17 |
| — | Security Update | 1.6.2-26 |
| — | Security Update | 8.4.0-24 |
| — | Security Update | 1.11.2-22 |
| — | Security Update | 1.2.0-21 |
| — | Security Update | 2.37.9-4 |
| — | Security Update | 3.2.236-21 |
🧭 EchelonGraph on CVE-2024-51744
- EchelonGraph score
- 3.1 LOW
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above.
Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2024-51744, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).