Skip to content

Configuration API in EdgeXFoundry 2.1.0 and earlier exposes message bus credentials to local unauthenticated users

Moderate
eb-oss published GHSA-g63h-q855-vp3q Jun 14, 2022

Package

No package listed

Affected versions

<2.1.1

Patched versions

>=v2.1.1
gomod github.com/edgexfoundry/app-functions-sdk-go/v2 (Go)
<2.1.1
2.1.1, 2.2.0
gomod github.com/edgexfoundry/device-sdk-go/v2 (Go)
<2.1.1
2.1.1, 2.2.0

Description

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

For more information

If you have any questions or comments about this advisory:

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

CVE ID

CVE-2022-31066

Credits