Multiple security issues in Pomerium's embedded envoy
Published 1 Mar 2022 · Updated 1 Mar 2022
Is your project on an affected github.com/pomerium/pomerium?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <0.16.4
- Fixed in
- 0.16.4
go get github.com/pomerium/pomerium@v0.16.4Details
Envoy, which Pomerium is based on, has issued multiple CVEs impacting stability and security.
Though Pomerium may not be vulnerable to all of the issues, it is recommended that all users upgrade to Pomerium v0.16.4 as soon as possible to minimize risk.
Impact
- Possible DoS or crash
- Resources available to unauthorized users
- Pomerium may trust upstream certificates that should not be trusted
Patches
Patched in v0.16.4
Workarounds
No
References
- CVE-2021-43824 (CVSS Score 6.5, Medium): Envoy 1.21.0 and earlier - Potential null pointer dereference when using JWT filter safe_regex match
- CVE-2021-43825 (CVSS Score 6.1, Medium): Envoy 1.21.0 and earlier - Use-after-free when response filters increase response data, and increased data exceeds downstream buffer limits.
- CVE-2021-43826 (CVSS Score 6.1, Medium): Envoy 1.21.0 and earlier - Use-after-free when tunneling TCP over HTTP, if downstream disconnects during upstream connection establishment
- CVE-2022-21654 (CVSS Score 7.3, High): Envoy 1.7.0 and later - Incorrect configuration handling allows mTLS session re-use without re-validation after validation settings have changed.
- CVE-2022-21655 (CVSS Score 7.5, High): Envoy 1.21 and earlier - Incorrect handling of internal redirects to routes with a direct response entry
- CVE-2022-21657 (CVSS Score 3.1, Low): Envoy 1.20.1 and earlier - X.509 Extended Key Usage and Trust Purposes bypass
For more information
If you have any questions or comments about this advisory:
Open an issue in pomerium/pomerium Email us at [security@pomerium.com](mailto:security@pomerium.com)
Is GHSA-j34v-3552-5r7j in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/pomerium/pomerium, and gives you the command that fixes it.
More advisories for github.com/pomerium/pomerium
- HighCVE-2026-50285Pomerium Pre-Auth Memory Exhaustion via Unbounded zstd Decompression in HPKE Callback · 15 Jul 2026
- LowCVE-2024-47616Pomerium service account access token may grant unintended access to databroker API in github.com/pomerium/pomerium · 9 Oct 2024
- HighCVE-2024-47616Pomerium service account access token may grant unintended access to databroker API · 2 Oct 2024
- MediumCVE-2022-24797Exposure of debug and metrics endpoints in Pomerium · 6 Sept 2024
- LowCVE-2021-39162Incorrect handling of H2 GOAWAY + SETTINGS frames in github.com/pomerium/pomerium · 21 Aug 2024
- LowCVE-2021-29652pomerium_signature is not verified in middleware in github.com/pomerium/pomerium · 21 Aug 2024
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.