Microsoft security update for CVE-2022-21698
🔗 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-2022-21698. This page also shows what EchelonGraph holds for CVE-2022-21698, 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 products24
- azl3 application-gateway-kubernetes-ingress 1.7.2-2 on Azure Linux 3.0
- azl3 application-gateway-kubernetes-ingress 1.7.2-3 on Azure Linux 3.0
- azl3 keda 2.14.0-1 on Azure Linux 3.0
- azl3 keda 2.4.0-15 on Azure Linux 3.0
- azl3 moby-engine 20.10.25-3 on Azure Linux 3.0
- azl3 moby-engine 25.0.3-1 on Azure Linux 3.0
- azl3 multus 3.8-13 on Azure Linux 3.0
- azl3 multus 4.0.2-1 on Azure Linux 3.0
- azl3 node-problem-detector 0.8.10-18 on Azure Linux 3.0
- azl3 node-problem-detector 0.8.15-1 on Azure Linux 3.0
- azl3 prometheus-process-exporter 0.7.10-15 on Azure Linux 3.0
- azl3 prometheus-process-exporter 0.8.2-1 on Azure Linux 3.0
- cbl2 application-gateway-kubernetes-ingress 1.4.0-25 on CBL Mariner 2.0
- cbl2 cri-o 1.22.3-14 on CBL Mariner 2.0
- cbl2 kube-vip-cloud-provider 0.0.2-22 on CBL Mariner 2.0
- cbl2 local-path-provisioner 0.0.21-18 on CBL Mariner 2.0
- cbl2 moby-buildx 0.7.1-24 on CBL Mariner 2.0
- cbl2 moby-cli 20.10.27-5 on CBL Mariner 2.0
- cbl2 moby-engine 20.10.27-4 on CBL Mariner 2.0
- cbl2 nmi 1.8.7-15 on CBL Mariner 2.0
- cbl2 node-problem-detector 0.8.10-20 on CBL Mariner 2.0
- cbl2 prometheus-node-exporter 1.3.1-26 on CBL Mariner 2.0
- cbl2 prometheus-process-exporter 0.7.10-21 on CBL Mariner 2.0
- cbl2 rook 1.6.2-26 on CBL Mariner 2.0
✅ Updates Microsoft lists: 18 updates
18 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 | 0.8.2-1 |
| — | Security Update | 0.8.15-1 |
| — | Security Update | 4.0.2-1 |
| — | Security Update | 25.0.3-1 |
| — | Security Update | 2.14.0-1 |
| — | Security Update | 1.7.2-2 |
| — | Security Update | 1.4.0-17 |
| — | Security Update | 0.7.1-16 |
| — | Security Update | 20.10.27-5 |
| — | Security Update | 20.10.27-3 |
| — | Security Update | 1.8.11-2 |
| — | Security Update | 0.7.10-18 |
| — | Security Update | 0.0.2-14 |
| — | Security Update | 0.0.21-14 |
| — | Security Update | 0.8.10-19 |
| — | Security Update | 1.3.1-23 |
| — | Security Update | 1.6.2-18 |
| — | Security Update | 1.21.7-2 |
🧭 EchelonGraph on CVE-2022-21698
- EchelonGraph score
- 7.5 HIGH
- 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
client_golang is the instrumentation library for Go applications in Prometheus, and the promhttp package in client_golang provides tooling around HTTP servers and clients. In client_golang prior to version 1.11.1, HTTP server is susceptible to a Denial of Service through unbounded cardinality, and potential memory exhaustion, when handling requests with non-standard HTTP methods. In order to be affected, an instrumented software must use any of `promhttp.InstrumentHandler*` middleware except `RequestsInFlight`; not filter any specific methods (e.g GET) before middleware; pass metric with `method` label name to our middleware; and not have any firewall/LB/proxy that filters away requests with unknown `method`. client_golang version 1.11.1 contains a patch for this issue. Several workarounds are available, including removing the `method` label name from counter/gauge used in the InstrumentHandler; turning off affected promhttp handlers; adding custom middleware before promhttp handler that will sanitize the request method given by Go http.Request; and using a reverse proxy or web application firewall, configured to only allow a limited set of methods.
Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2022-21698, 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).