Vulnerability in github.com/projectcontour/contour (CVE-2021-32783)
Summary
Vulnerability in github.com/projectcontour/contour (CVE-2021-32783). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.17.1 or later.
Original description
The description as published by the source.
Contour is a Kubernetes ingress controller using Envoy proxy. In Contour before version 1.17.1 a specially crafted ExternalName type Service may be used to access Envoy's admin interface, which Contour normally prevents from access outside the Envoy container. This can be used to shut down Envoy remotely (a denial of service), or to expose the existence of any Secret that Envoy is using for its configuration, including most notably TLS Keypairs. However, it cannot be used to get the content of those secrets. Since this attack allows access to the administration interface, a variety of administration options are available, such as shutting down the Envoy or draining traffic. In general, the Envoy admin interface cannot easily be used for making changes to the cluster, in-flight requests, or backend services, but it could be used to shut down or drain Envoy, change traffic routing, or to retrieve secret metadata, as mentioned above. The issue will be addressed in Contour v1.18.0 and a cherry-picked patch release, v1.17.1, has been released to cover users who cannot upgrade at this time. For more details refer to the linked GitHub Security Advisory.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-32783 has been found in github.com/projectcontour/contour.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/projectcontour/contour to 1.17.1 or later.
If unsure, ask your IT team or search "github.com/projectcontour/contour CVE-2021-32783" on the vendor's site.
CVE-2021-32783 (github.com/projectcontour/contour) — CWE-610
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.17.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-610) exists in github.com/projectcontour/contour.
Check the vendor advisory for the affected versions of github.com/projectcontour/contour.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.17.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/projectcontour/contour' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/projectcontour/contour' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/projectcontour/contourを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/projectcontour/contour to 1.17.1ステージング環境で 1.17.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com