Skip to main content

CVE-2022-31066: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in edgexfoundry edgex-go

Medium
Published: Tue Jun 14 2022 (06/14/2022, 21:55:11 UTC)
Source: CVE
Vendor/Project: edgexfoundry
Product: edgex-go

Description

EdgeX Foundry is an open source project for building a common open framework for Internet of Things edge computing. Prior to version 2.1.1, 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. Users should upgrade to EdgeXFoundry Kamakura release (2.2.0) or to the June 2022 EdgeXFoundry LTS Jakarta release (2.1.1) to receive a patch. More information about which go modules, docker containers, and snaps contain patches is available in the GitHub Security Advisory. There are currently no known workarounds for this issue.

AI-Powered Analysis

AILast updated: 06/23/2025, 04:51:34 UTC

Technical Analysis

CVE-2022-31066 is a vulnerability identified in the edgex-go component of EdgeX Foundry, an open-source framework designed for Internet of Things (IoT) edge computing. The flaw exists in versions prior to 2.1.1 and concerns the /api/v2/config endpoint, which improperly exposes message bus credentials to local unauthenticated users when the system is running in security-enabled mode. Normally, these credentials should be securely stored in the EdgeX secret store and require authentication to access. However, due to this vulnerability, access controls are bypassed, allowing any local user without authentication to retrieve sensitive message bus credentials. In security-disabled mode, no credentials are required to access the message bus, so the vulnerability primarily impacts security-enabled deployments. Exploiting this flaw enables an attacker with local access to intercept messages transmitted over the EdgeX message bus or inject malicious or fabricated data into the bus, potentially compromising the integrity and confidentiality of IoT data flows. The vulnerability affects multiple distribution formats including go modules, Docker containers, and snaps, with patches available in EdgeX Foundry Kamakura release (2.2.0) and the June 2022 LTS Jakarta release (2.1.1). No known workarounds exist, making upgrading the only effective remediation. There are no known exploits in the wild at this time. This vulnerability is classified under CWE-200, indicating exposure of sensitive information to unauthorized actors. The issue arises from improper access control and insufficient protection of sensitive credentials within the system's API endpoints, a critical concern for IoT edge computing environments where data integrity and confidentiality are paramount.

Potential Impact

For European organizations deploying EdgeX Foundry in IoT edge computing environments, this vulnerability poses a significant risk to the confidentiality and integrity of sensitive data transmitted across the message bus. Unauthorized local users gaining access to message bus credentials can eavesdrop on sensitive telemetry or control messages, potentially leading to data leakage or espionage. Furthermore, the ability to inject fabricated data into the message bus can disrupt operational processes, cause erroneous device behavior, or trigger false alarms, impacting availability and reliability of IoT services. This is particularly critical in industrial IoT (IIoT) deployments common in manufacturing, energy, and critical infrastructure sectors across Europe. Compromise of edge computing nodes could cascade to broader network effects, undermining trust in IoT systems and causing operational downtime. Given the lack of known exploits, the immediate risk is moderate, but the potential for targeted attacks in sensitive environments remains high, especially where local access controls are weak or insider threats exist.

Mitigation Recommendations

The primary mitigation is to upgrade all affected EdgeX Foundry deployments to version 2.1.1 or later, such as the Kamakura release (2.2.0) or the June 2022 LTS Jakarta release (2.1.1), which contain patches addressing this vulnerability. Organizations should audit their IoT edge nodes to identify versions of edgex-go in use and prioritize patching accordingly. Since no workarounds exist, restricting local access to edge devices is critical; implement strict physical and network access controls to prevent unauthorized local users from interacting with the device. Employ host-based intrusion detection systems (HIDS) and monitor API endpoint access logs for suspicious activity. Additionally, consider deploying network segmentation to isolate edge computing nodes from less trusted networks and users. Review and harden authentication and authorization configurations in EdgeX Foundry to ensure security-enabled mode is properly enforced. Finally, integrate this vulnerability into vulnerability management and incident response processes to ensure timely detection and remediation of any exploitation attempts.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2022-05-18T00:00:00.000Z
Cisa Enriched
true

Threat ID: 682d9844c4522896dcbf348b

Added to database: 5/21/2025, 9:09:24 AM

Last enriched: 6/23/2025, 4:51:34 AM

Last updated: 8/11/2025, 7:26:47 AM

Views: 13

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats