How severe is GHSA-g63h-q855-vp3q?

GHSA-g63h-q855-vp3q has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-g63h-q855-vp3q?

GHSA-g63h-q855-vp3q affects the following packages: github.com/edgexfoundry/device-sdk-go/v2 (Go), github.com/edgexfoundry/app-functions-sdk-go/v2 (Go). Ecosystems affected: Go.

How do I fix GHSA-g63h-q855-vp3q?

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 GHSA-g63h-q855-vp3q is resolved across your whole dependency graph.

How do I detect GHSA-g63h-q855-vp3q in my Go dependencies?

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.

How do I mitigate GHSA-g63h-q855-vp3q if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-g63h-q855-vp3q actively exploited in the wild?

No public exploit code has been indexed for GHSA-g63h-q855-vp3q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-g63h-q855-vp3q?

GHSA-g63h-q855-vp3q has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-g63h-q855-vp3q?

GHSA-g63h-q855-vp3q is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g63h-q855-vp3q published, and has it been updated?

GHSA-g63h-q855-vp3q was published on June 17, 2022 and was last updated on August 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

Configuration API in EdgeXFoundry 2.1.0 and earlier exposes message bus credentials to local unauthenticated usersGHSA-g63h-q855-vp3q

MEDIUMFix: edgexfoundry/device-sdk-go#1161

GHSA-g63h-q855-vp3q 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.

Also known asCVE-2022-31066GO-2022-0491

Published

Jun 17, 2022

Updated

Aug 21, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 GHSA-g63h-q855-vp3q.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs25th percentile — riskier than 25% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐹github.com/edgexfoundry/device-sdk-go/v2🐹github.com/edgexfoundry/app-functions-sdk-go/v2

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

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/edgexfoundry/device-sdk-go/v2`	all versions	2.1.1`go get github.com/edgexfoundry/device-sdk-go/v2@v2.1.1`
🐹Go	`github.com/edgexfoundry/app-functions-sdk-go/v2`	all versions	2.1.1`go get github.com/edgexfoundry/app-functions-sdk-go/v2@v2.1.1`

Affected Products

1 product · 1 configurations

Application

edgex foundryedgexfoundry

< 2.1.1

range

Detection & mitigation playbook

Open-source dependency

Detect
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 GHSA-g63h-q855-vp3q is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

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