CVE-2021-32783: Github.com/projectcontour/contour ExternalName Services Can Be Used Vulnerability

HIGH
Advisory Identifier: GHSA-5ph6-qq5x-7jwc
CVSS 8.5
CWE-610
Published
Advisory Summary

CVE-2021-32783 is a HIGH (CVSS 8.5) externalname services can be used vulnerability (CWE-610: Externally Controlled Reference to a Resource in Another Sphere) affecting Github.com/projectcontour/contour libraries in the Go ecosystem. The issue involves externalname services can be used to gain access to envoy's admin interface. Remediation is available by upgrading affected packages to version 1.14.2, 1.15.2, 1.16.1, 1.17.1.

CVE-2021-32783 at a Glance

CVE Identifier CVE-2021-32783
GHSA Identifier GHSA-5ph6-qq5x-7jwc
Severity HIGH
CVSS v3.1 Base Score 8.5
CWE Classification CWE-610: Externally Controlled Reference to a Resource in Another Sphere
Affected Product Github.com/projectcontour/contour
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2021-32783

To remediate this vulnerability, upgrade all affected Github.com/projectcontour/contour dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/projectcontour/contour fixed: 1.14.2
Upgrade github.com/projectcontour/contour to 1.14.2
github.com/projectcontour/contour fixed: 1.15.2
Upgrade github.com/projectcontour/contour to 1.15.2
github.com/projectcontour/contour fixed: 1.16.1
Upgrade github.com/projectcontour/contour to 1.16.1
github.com/projectcontour/contour fixed: 1.17.1
Upgrade github.com/projectcontour/contour to 1.17.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/projectcontour/contour

How to Check if You Are Affected

To determine whether your application is affected by CVE-2021-32783, inspect your project dependencies for Github.com/projectcontour/contour:

inspect dependencies for github.com/projectcontour/contour

Analyze the terminal output to locate any version of Github.com/projectcontour/contour in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.14.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-610: Externally Controlled Reference to a Resource in Another Sphere, where the product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere. In Github.com/projectcontour/contour, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Josh Ferrell (@josh-ferrell) from VMware has reported that 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. ### Patches The issue will be addressed in the forthcoming Contour v1.18.0 and a patch release, v1.17.1, has been released in the meantime. It is addressed in two ways: - disabling ExternalName type Services by default - When ExternalName Services are enabled, block obvious "localhost" entries. #### Disable ExternalName type Services by default This change prohibits processing of ExternalName services unless the cluster operator specifically allows them using the new `--enable-externalname` flag or equivalent configuration file setting. This is a breaking change for previous versions of Contour, which is unfortunate, but necessary because of the severity of the information exposed in this advisory. #### Block obvious `localhost` entries for enabled ExternalName Services As part of this change set, we have added a filter in the event that operators *do* enable ExternalName Services, such that obvious `localhost` entries are rejected by Contour. There are a number of problems with this method, however: - This is a porous control. As long as you control a domain name, it's trivially easy to add a DNS entry for any name you like that redirects to `127.0.0.1` or `::1`. Contour even provides `local.projectcontour.io` ourselves for testing and example purposes. (This name is, of course, included in the "obvious localhost entries" list.) So we can never totally stop this exploit as long as the admin interface is accessible on localhost, which, according to envoyproxy/envoy#2763, will be for some time if not forever. The best we can do is block some obvious elements, but this is always a risk for a motivated attacker. - We've actually suggested using `localhost` ExternalName Services in the past, to allow people to connect to sidecar External Authentication services in their cluster. Both of these changes break this use-case, but given that it's about something that has security requirements high enough to require authentication, it's important to ensure that people are opting in. For the External Auth sidecar case, we are investigating an update to ExtensionService that will help with the sidecar use case. ### Workarounds Not easily. It's not possible to control the creation of ExternalName Services with RBAC without the use of Gatekeeper or other form of admission control, and the creation of services is required for Contour to actually work for application developer personas. ### For more information Exploit code will be published at a later date for this vulnerability, once our users have had a chance to upgrade.

CVE-2021-32783 Affected Github.com/projectcontour/contour Versions

4 component(s)
Fixed Versions:
1.14.21.15.21.16.11.17.1
Product / Package Ecosystem Affected Versions Fixed Version
github.com/projectcontour/contour
Go
< 1.14.2
1.14.2
github.com/projectcontour/contour
Go
≥ 1.15.0
< 1.15.2
1.15.2
github.com/projectcontour/contour
Go
≥ 1.16.0
< 1.16.1
All 1 versions
1.16.0
1.16.1
github.com/projectcontour/contour
Go
≥ 1.17.0
< 1.17.1
All 1 versions
1.17.0
1.17.1

References

Frequently Asked Questions

What is CVE-2021-32783?
CVE-2021-32783 is a security vulnerability in Github.com/projectcontour/contour involving ExternalName Services can be used to gain access to Envoy's admin interface under CWE-610: Externally Controlled Reference to a Resource in Another Sphere.
Which Github.com/projectcontour/contour versions are affected?
Affected versions include releases prior to 1.14.2, 1.15.2, 1.16.1, 1.17.1 across affected packages: github.com/projectcontour/contour.
What version fixes CVE-2021-32783?
Upgrading to 1.14.2, 1.15.2, 1.16.1, 1.17.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/projectcontour/contour affected?
Yes, github.com/projectcontour/contour is affected in releases prior to 1.14.2, 1.15.2, 1.16.1, 1.17.1. Upgrade your dependency to 1.14.2, 1.15.2, 1.16.1, 1.17.1 or later.
What is the CVSS score of CVE-2021-32783?
CVE-2021-32783 has a CVSS v3.1 base score of 8.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H.
What CWE is associated with CVE-2021-32783?
CVE-2021-32783 is classified under CWE-610: Externally Controlled Reference to a Resource in Another Sphere (The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.).
How can I check Go dependencies for CVE-2021-32783?
Run the dependency tree command: 'inspect dependencies for github.com/projectcontour/contour'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5ph6-qq5x-7jwc",
  "modified" : "2021-08-30T16:53:38Z",
  "published" : "2021-08-30T17:22:10Z",
  "aliases" : [ "CVE-2021-32783" ],
  "summary" : "ExternalName Services can be used to gain access to Envoy's admin interface",
  "details" : "### Impact\nJosh Ferrell (@josh-ferrell) from VMware has reported that 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.\n\nSince 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.\n\n### Patches\nThe issue will be addressed in the forthcoming Contour v1.18.0 and a patch release, v1.17.1, has been released in the meantime.\n\nIt is addressed in two ways:\n- disabling ExternalName type Services by default\n- When ExternalName Services are enabled, block obvious \"localhost\" entries.\n\n#### Disable ExternalName type Services by default\n\nThis change prohibits processing of ExternalName services unless the cluster operator specifically allows them using the new `--enable-externalname` flag or equivalent configuration file setting. This is a breaking change for previous versions of Contour, which is unfortunate, but necessary because of the severity of the information exposed in this advisory.\n\n\n#### Block obvious `localhost` entries for enabled ExternalName Services\n\nAs part of this change set, we have added a filter in the event that operators *do* enable ExternalName Services, such that obvious `localhost` entries are rejected by Contour.\n\nThere are a number of problems with this method, however:\n- This is a porous control. As long as you control a domain name, it's trivially easy to add a DNS entry for any name you like that redirects to `127.0.0.1` or `::1`. Contour even provides `local.projectcontour.io` ourselves for testing and example purposes. (This name is, of course, included in the \"obvious localhost entries\" list.) So we can never totally stop this exploit as long as the admin interface is accessible on localhost, which, according to envoyproxy/envoy#2763, will be for some time if not forever. The best we can do is block some obvious elements, but this is always a risk for a motivated attacker.\n- We've actually suggested using `localhost` ExternalName Services in the past, to allow people to connect to sidecar External Authentication services in their cluster. Both of these changes break this use-case, but given that it's about something that has security requirements high enough to require authentication, it's important to ensure that people are opting in. For the External Auth sidecar case, we are investigating an update to ExtensionService that will help with the sidecar use case.\n\n### Workarounds\nNot easily. It's not possible to control the creation of ExternalName Services with RBAC without the use of Gatekeeper or other form of admission control, and the creation of services is required for Contour to actually work for application developer personas.\n\n### For more information\nExploit code will be published at a later date for this vulnerability, once our users have had a chance to upgrade.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/projectcontour/contour"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.14.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/projectcontour/contour"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.15.0"
      }, {
        "fixed" : "1.15.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/projectcontour/contour"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.16.0"
      }, {
        "fixed" : "1.16.1"
      } ]
    } ],
    "versions" : [ "1.16.0" ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/projectcontour/contour"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.17.0"
      }, {
        "fixed" : "1.17.1"
      } ]
    } ],
    "versions" : [ "1.17.0" ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/projectcontour/contour/security/advisories/GHSA-5ph6-qq5x-7jwc"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2021-32783"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/projectcontour/contour/commit/5f3e6d0ab1d48e64bae46400c85c490b200393a3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/projectcontour/contour/commit/b53a5c4fd927f4ea2c6cf02f1359d8e28bef852e"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/projectcontour/contour/releases/tag/v1.14.2"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/projectcontour/contour/releases/tag/v1.15.2"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/projectcontour/contour/releases/tag/v1.16.1"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/projectcontour/contour/releases/tag/v1.17.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-610" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-08-30T16:53:38Z",
    "nvd_published_at" : "2021-07-23T22:15:00Z"
  }
}