Configuration API in EdgeXFoundry 2.1.0 and earlier exposes message bus credentials to local unauthenticated users
CVE-2022-31066GHSA-g63h-q855-vp3q
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/edgexfoundry/app-functions-sdk-go/v2 2.1.1; github.com/edgexfoundry/device-sdk-go/v2 2.1.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/edgexfoundry/app-functions-sdk-go/v2
- Affected
- < 2.1.1
- Fixed in
- 2.1.1
Go github.com/edgexfoundry/device-sdk-go/v2
- Affected
- < 2.1.1
- Fixed in
- 2.1.1
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-g63h-q855-vp3q lists affected ranges: Go github.com/edgexfoundry/device-sdk-go/v2 >=0 =0 <2.1.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.9 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
- EPSS
- CVE-2022-31066: 0.32% estimated exploitation activity in the next 30 days; percentile 25.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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 -…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-g63h-q855-vp3q
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2022-31066 Advisory: Configuration API in EdgeXFoundry 2.1.0 and earlier exposes message bus credentials to local unauthenticated users IDs: CVE-2022-31066, GHSA-g63h-q855-vp3q Record: https://patchnext.com/advisories/cve-2022-31066 (revision 1, source checked 26 Oct 2026, 14:54 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/edgexfoundry/app-functions-sdk-go/v2 2.1.1; github.com/edgexfoundry/device-sdk-go/v2 2.1.1. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/edgexfoundry/app-functions-sdk-go/v2: affected < 2.1.1; fixed in 2.1.1 - Go github.com/edgexfoundry/device-sdk-go/v2: affected < 2.1.1; fixed in 2.1.1 ## Suggested inspection (read-only) - Go github.com/edgexfoundry/app-functions-sdk-go/v2: check the installed version with your package manager. - Go github.com/edgexfoundry/device-sdk-go/v2: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/edgexfoundry/app-functions-sdk-go/v2, github.com/edgexfoundry/device-sdk-go/v2. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-g63h-q855-vp3q (GitHub-reviewed advisory GHSA-g63h-q855-vp3q lists affected ranges: Go github.com/edgexfoundry/device-sdk-go/v2 >=0 =0 <2.1.1) Commands are suggestions: review each one before running it.
Loading voting…