Security readout for executives and security teams
Plain-English summary
A local unauthenticated user could obtain EdgeX message bus credentials from a configuration API. In security-enabled deployments, those credentials should be protected in the secret store. Exposure could let an attacker observe data moving through the bus or inject false data into edge workflows.
Executive priority
Prioritize remediation for EdgeX deployments on shared or high-trust edge hosts. The bug is not remotely exploitable from the provided evidence, but leaked bus credentials can undermine data integrity in IoT workflows.
Technical view
CVE-2022-31066 affects edgexfoundry edgex-go before 2.1.1. The /api/v2/config endpoint exposes message bus credentials to local unauthenticated users, bypassing intended secret-store access controls in security-enabled mode. CVSS is 5.9 with local attack vector and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is primarily local: systems running edgex-go before 2.1.1 where a local user or process can reach the configuration API. The issue is described for security-enabled mode; security-disabled mode does not require message bus credentials.
Exploitation context
The provided sources do not report active exploitation, and KEV is false. Risk is higher on shared hosts, edge gateways with multiple local services, or environments where a compromised local process can access EdgeX APIs.
Researcher notes
Focus analysis on local API reachability, edgex-go version, security-enabled configuration, and whether credentials may have been exposed before patching. The sources name no workaround and do not provide evidence of exploitation in the wild.
Mitigation direction
- Upgrade to EdgeX Foundry Kamakura 2.2.0 or Jakarta LTS 2.1.1.
- Review the GitHub advisory for patched modules, containers, and snaps.
- Treat exposed message bus credentials as compromised where vulnerable versions were locally accessible.
- Check vendor guidance because the sources state no known workaround.
Validation and detection
- Inventory EdgeX Foundry edgex-go deployments and identify versions earlier than 2.1.1.
- Confirm whether security-enabled mode is used on affected deployments.
- Review local access paths to the configuration API on edge hosts.
- After upgrading, verify deployed modules, containers, or snaps match patched versions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-31066 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L2.53.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.9MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/edgexfoundry/edgex-go/security/advisories/GHSA-g63h-q855-vp3qCVE reference · x_refsource_CONFIRM
- https://github.com/edgexfoundry/device-sdk-go/pull/1161CVE reference · x_refsource_MISC
- https://github.com/edgexfoundry/edgex-go/pull/4016CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.