Advisory

GHSA-j34v-3552-5r7j

Also known as: None

Summary

Multiple security issues in Pomerium's embedded envoy

Details

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

Envoy Security Announcement

  • 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 [[email protected]](mailto:[email protected])

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2022-03-01 22:04 UTC
Modified
2022-03-01 22:04 UTC

Affected packages and fixes

github.com/pomerium/pomerium

Go · All systems

Affected

  • introduced 0, fixed 0.16.4 (semver)

Fixed versions

0.16.4

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences