Configuration API in EdgeXFoundry 2.1.0 and earlier exposes message bus credentials to local unauthenticated users
Date: 2022-06
Affected: go/github.com/edgexfoundry/app-functions-sdk-go/v2, go/github.com/edgexfoundry/device-sdk-go/v2
Attack vector: auth-bypass
Category: vulnerability-disclosure
Severity: Medium
CVE: CVE-2022-31066
CWE: CWE-200
CVSS: 5.9 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L)

### 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


Mitigations:

Architectural layers (MAESTRO):