Hi
Is the airlock microgateway affected by https://github.com/envoyproxy/envoy/security/advisories/GHSA-3wvj-j6qm-62mr. ?
Can you disclose the affected and the patched versions after the responsible disclosure?
Kind regards
Hi
Is the airlock microgateway affected by https://github.com/envoyproxy/envoy/security/advisories/GHSA-3wvj-j6qm-62mr. ?
Can you disclose the affected and the patched versions after the responsible disclosure?
Kind regards
Thank you for bringing this up.
As you have correctly pointed out: Envoy has fixed the issue in the versions v1.39.3, v1.38.6 and v1.37.8.
Airlock Microgateway versions 5.2.1, 5.1.7 and 5.0.10 include Envoy versions v1.39.4, v1.38.7 and v1.37.9 respectively and thus provide a fix for the issue at hand.
Airlock Microgateway versions below 5.2.1, 5.1.7 and 5.0.10 are affected.
Note that you can also consult our SBOM to get information on dependencies. Furthermore, the release notes on Github always inform you if a patch release containes an update of Envoy, e.g., for 5.2.1
Hope that helps.
Best regards,
Christoph
How exactly would this be exploitable in Airlock Microgateway, I don’t see where one can configure compression? In envoy this setting is found via BackendTrafficPolicySpec and ProxyPrometheusProvider.
It would be exploitable if you use Microgateway’s EnvoyExtensionPolicy and configure the Envoy Decompression filter.
At least, that is our theoretical assumption. We have not conducted a PoC or similar.