ghsa-g63h-q855-vp3q
Vulnerability from github
Published
2022-06-17 01:11
Modified
2022-07-11 21:21
Summary
Configuration API in EdgeXFoundry 2.1.0 and earlier exposes message bus credentials to local unauthenticated users
Details

Impact

The /api/v2/config endpoint exposes message bus credentials to local unauthenticated users. In security-enabled mode, message bus credentials are supposed to be kept in the EdgeX secret store and require authentication to access. This vulnerability bypasses the access controls on message bus credentials when running in security-enabled mode. (No credentials are required when running in security-disabled mode.) As a result, attackers could intercept data or inject fake data into the EdgeX message bus.

Patches

Users should upgrade to EdgeXFoundry Kamakura release (2.2.0) or to the June 2022 EdgeXFoundry LTS Jakarta release (2.1.1).

The issue has been patched in the following docker containers and snaps:

Patched go modules

github.com/edgexfoundry/device-sdk-go/v2 >= v2.1.1 github.com/edgexfoundry/app-functions-sdk-go/v2 >= v2.1.1

Patched docker containers

URL: https://hub.docker.com/r/edgexfoundry - docker.io/edgexfoundry/core-metadata:>=2.1.1 - docker.io/edgexfoundry/core-metadata-arm64:>=2.1.1 - docker.io/edgexfoundry/core-data:>=2.1.1 - docker.io/edgexfoundry/core-data-arm64:>=2.1.1 - docker.io/edgexfoundry/core-command:>=2.1.1 - docker.io/edgexfoundry/core-command-arm64:>=2.1.1 - docker.io/edgexfoundry/support-notifications:>=2.1.1 - docker.io/edgexfoundry/support-notifications-arm64:>=2.1.1 - docker.io/edgexfoundry/support-scheduler:>=2.1.1 - docker.io/edgexfoundry/support-scheduler-arm64:>=2.1.1 - docker.io/edgexfoundry/sys-mgmt-agent:>=2.1.1 - docker.io/edgexfoundry/sys-mgmt-agent-arm64:>=2.1.1 - docker.io/edgexfoundry/security-proxy-setup:>=2.1.1 - docker.io/edgexfoundry/security-proxy-setup-arm64:>=2.1.1 - docker.io/edgexfoundry/security-secretstore-setup:>=2.1.1 - docker.io/edgexfoundry/security-secretstore-setup-arm64:>=2.1.1 - docker.io/edgexfoundry/security-bootstrapper:>=2.1.1 - docker.io/edgexfoundry/security-bootstrapper-arm64:>=2.1.1 - docker.io/edgexfoundry/app-rfid-llrp-inventory:>=2.1.1 - docker.io/edgexfoundry/app-rfid-llrp-inventory-arm64:>=2.1.1 - docker.io/edgexfoundry/app-service-configurable:>=2.1.1 - docker.io/edgexfoundry/app-service-configurable-arm64:>=2.1.1 - docker.io/edgexfoundry/device-camera:>=2.2.0 - docker.io/edgexfoundry/device-camera-arm64:>=2.2.0 - docker.io/edgexfoundry/device-gpio:>=2.1.1 - docker.io/edgexfoundry/device-gpio-arm64:>=2.1.1 - docker.io/edgexfoundry/device-modbus:>=2.1.1 - docker.io/edgexfoundry/device-modbus-arm64:>=2.1.1 - docker.io/edgexfoundry/device-mqtt:>=2.1.1 - docker.io/edgexfoundry/device-mqtt-arm64:>=2.1.1 - docker.io/edgexfoundry/device-rest:>=2.1.1 - docker.io/edgexfoundry/device-rest-arm64:>=2.1.1 - docker.io/edgexfoundry/device-rfid-llrp:>=2.1.1 - docker.io/edgexfoundry/device-rfid-llrp-arm64:>=2.1.1 - docker.io/edgexfoundry/device-snmp:>=2.1.1 - docker.io/edgexfoundry/device-snmp-arm64:>=2.1.1 - docker.io/edgexfoundry/device-virtual:>=2.1.1 - docker.io/edgexfoundry/device-virtual-arm64:>=2.1.1

Patched snaps

URL: https://snapcraft.io/edgexfoundry edgexfoundry 2.1/stable (will be automatically upgraded to 2.1.1)

Workarounds

No workaround available.

References

  • https://github.com/edgexfoundry/edgex-go/security/advisories/GHSA-g63h-q855-vp3q
  • https://github.com/edgexfoundry/device-sdk-go/pull/1161 (patch against Kamakura)
  • https://github.com/edgexfoundry/edgex-go/pull/4016 (patch against Kamakura)
  • https://github.com/edgexfoundry/edgex-go/pull/4039 (cherry-pick patch against Jakarta)
  • https://github.com/edgexfoundry/device-sdk-go/pull/1167 (differs from patch on main: don't copy PW in vs delete it after)

For more information

If you have any questions or comments about this advisory: * Contact us in the Slack #security channel * Open an issue in edgex-go * Email us at EdgeX-TSC-Security@lists.edgexfoundry.org

Show details on source website


{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/edgexfoundry/device-sdk-go/v2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.1.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/edgexfoundry/app-functions-sdk-go/v2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.1.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2022-31066"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2022-06-17T01:11:42Z",
    "nvd_published_at": "2022-06-14T22:15:00Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\nThe /api/v2/config endpoint exposes message bus credentials to local unauthenticated users.  In security-enabled mode, message bus credentials are supposed to be kept in the EdgeX secret store and require authentication to access.  This vulnerability bypasses the access controls on message bus credentials when running in security-enabled mode.  (No credentials are required when running in security-disabled mode.)  As a result, attackers could intercept data or inject fake data into the EdgeX message bus.\n\n### Patches\nUsers should upgrade to EdgeXFoundry Kamakura release (2.2.0) or to the June 2022 EdgeXFoundry LTS Jakarta release (2.1.1).\n\nThe issue has been patched in the following docker containers and snaps:\n\n#### Patched go modules\ngithub.com/edgexfoundry/device-sdk-go/v2 \u003e= v2.1.1\ngithub.com/edgexfoundry/app-functions-sdk-go/v2 \u003e= v2.1.1\n\n#### Patched docker containers\nURL: https://hub.docker.com/r/edgexfoundry\n- docker.io/edgexfoundry/core-metadata:\u003e=2.1.1\n- docker.io/edgexfoundry/core-metadata-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/core-data:\u003e=2.1.1\n- docker.io/edgexfoundry/core-data-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/core-command:\u003e=2.1.1\n- docker.io/edgexfoundry/core-command-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/support-notifications:\u003e=2.1.1\n- docker.io/edgexfoundry/support-notifications-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/support-scheduler:\u003e=2.1.1\n- docker.io/edgexfoundry/support-scheduler-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/sys-mgmt-agent:\u003e=2.1.1\n- docker.io/edgexfoundry/sys-mgmt-agent-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/security-proxy-setup:\u003e=2.1.1\n- docker.io/edgexfoundry/security-proxy-setup-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/security-secretstore-setup:\u003e=2.1.1\n- docker.io/edgexfoundry/security-secretstore-setup-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/security-bootstrapper:\u003e=2.1.1\n- docker.io/edgexfoundry/security-bootstrapper-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/app-rfid-llrp-inventory:\u003e=2.1.1\n- docker.io/edgexfoundry/app-rfid-llrp-inventory-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/app-service-configurable:\u003e=2.1.1\n- docker.io/edgexfoundry/app-service-configurable-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/device-camera:\u003e=2.2.0\n- docker.io/edgexfoundry/device-camera-arm64:\u003e=2.2.0\n- docker.io/edgexfoundry/device-gpio:\u003e=2.1.1\n- docker.io/edgexfoundry/device-gpio-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/device-modbus:\u003e=2.1.1\n- docker.io/edgexfoundry/device-modbus-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/device-mqtt:\u003e=2.1.1\n- docker.io/edgexfoundry/device-mqtt-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/device-rest:\u003e=2.1.1\n- docker.io/edgexfoundry/device-rest-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/device-rfid-llrp:\u003e=2.1.1\n- docker.io/edgexfoundry/device-rfid-llrp-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/device-snmp:\u003e=2.1.1\n- docker.io/edgexfoundry/device-snmp-arm64:\u003e=2.1.1\n- docker.io/edgexfoundry/device-virtual:\u003e=2.1.1\n- docker.io/edgexfoundry/device-virtual-arm64:\u003e=2.1.1\n\n#### Patched snaps\nURL: https://snapcraft.io/edgexfoundry\nedgexfoundry  2.1/stable  (will be automatically upgraded to 2.1.1)\n\n### Workarounds\nNo workaround available.\n\n### References\n* https://github.com/edgexfoundry/edgex-go/security/advisories/GHSA-g63h-q855-vp3q\n* https://github.com/edgexfoundry/device-sdk-go/pull/1161 (patch against Kamakura)\n* https://github.com/edgexfoundry/edgex-go/pull/4016 (patch against Kamakura)\n* https://github.com/edgexfoundry/edgex-go/pull/4039 (cherry-pick patch against Jakarta)\n* https://github.com/edgexfoundry/device-sdk-go/pull/1167 (differs from patch on main: don\u0027t copy PW in vs delete it after)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Contact us in the [Slack #security channel](https://slack.edgexfoundry.org/)\n* Open an issue in [edgex-go](https://github.com/edgexfoundry/edgex-go)\n* Email us at [EdgeX-TSC-Security@lists.edgexfoundry.org](mailto:EdgeX-TSC-Security@lists.edgexfoundry.org)\n",
  "id": "GHSA-g63h-q855-vp3q",
  "modified": "2022-07-11T21:21:42Z",
  "published": "2022-06-17T01:11:42Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/edgexfoundry/edgex-go/security/advisories/GHSA-g63h-q855-vp3q"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-31066"
    },
    {
      "type": "WEB",
      "url": "https://github.com/edgexfoundry/device-sdk-go/pull/1161"
    },
    {
      "type": "WEB",
      "url": "https://github.com/edgexfoundry/edgex-go/pull/4016"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/edgexfoundry/edgex-go"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Configuration API in EdgeXFoundry 2.1.0 and earlier exposes message bus credentials to local unauthenticated users"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…