CVE-2022-31066 is a medium-severity (CVSS 5.9) Information Exposure vulnerability in github.com/edgexfoundry/device-sdk-go/v2. A fix is available for github.com/edgexfoundry/device-sdk-go/v2 — see the affected versions and patch details below.
Configuration API in EdgeXFoundry exposes message bus credentials to local unauthenticated users
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-31066.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-31066 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/edgexfoundry/device-sdk-go/v2🐹github.com/edgexfoundry/app-functions-sdk-go/v2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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
- 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 [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/edgexfoundry/device-sdk-go/v2 | all versions | 2.1.1go get github.com/edgexfoundry/device-sdk-go/v2@v2.1.1 |
| 🐹Go | github.com/edgexfoundry/app-functions-sdk-go/v2 | all versions | 2.1.1go get github.com/edgexfoundry/app-functions-sdk-go/v2@v2.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/edgexfoundry/device-sdk-go/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/edgexfoundry/device-sdk-go/v2 to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31066 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-31066 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-31066. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-31066 in your dependencies?
O3 Security finds CVE-2022-31066 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.