Security readout for executives and security teams
Plain-English summary
CVE-2021-32753 affects EdgeX Foundry Edinburgh, Fuji, Geneva, and Hanoi. In OAuth2 mode, proxy user credentials can be weak because the client ID and secret are set to the proxy username. An unauthenticated remote attacker could obtain an authentication token and call EdgeX microservices from an untrusted network.
Executive priority
Treat as high priority where affected EdgeX gateways are reachable from untrusted networks. The issue can let outsiders obtain authenticated access to IoT edge services, which may affect confidentiality, integrity, and availability.
Technical view
The EdgeX API gateway OAuth2 setup creates proxy users where client_id and client_secret equal the proxy username. This weak-secret design enables dictionary-based token acquisition against the OAuth2 token endpoint, then authenticated access to EdgeX microservices. OAuth2 was default in Edinburgh; Fuji and later changed default authentication to JWT. Fixed direction is EdgeX Ireland, where OAuth2 is disabled.
Likely exposure
Exposure is likely limited to EdgeX Foundry Edinburgh, Fuji, Geneva, or Hanoi deployments using the API gateway with OAuth2 enabled and proxy users created by security-proxy-setup. Internet- or untrusted-network-reachable API gateway token endpoints increase business risk.
Exploitation context
The source bundle does not indicate CISA KEV listing or known active exploitation. The attack is remote, unauthenticated, low complexity, and requires OAuth2 mode with the affected proxy-user credential pattern. CVSS is 8.3 high.
Researcher notes
Focus validation on release version, authentication mode, and how OAuth2 consumers were created. Do not assume JWT deployments are affected from the provided evidence. The source bundle names EdgeX edgex-go releases and the Kong OAuth2 consumer creation path but does not provide broader product impact.
Mitigation direction
- Upgrade affected deployments to the EdgeX Ireland release.
- Do not rely on OAuth2 in Ireland; the advisory says it is disabled there.
- If OAuth2 is required pre-upgrade, create users directly with the Kong admin API.
- Avoid using security-proxy-setup to create OAuth2 users on affected releases.
- Review EdgeX advisory guidance before retaining affected OAuth2 configurations.
Validation and detection
- Inventory EdgeX deployments and identify Edinburgh, Fuji, Geneva, and Hanoi releases.
- Check whether the API gateway is configured for OAuth2 authentication.
- Identify proxy users created through security-proxy-setup.
- Confirm whether token endpoints are reachable from untrusted networks.
- Verify upgrade status or documented Kong-admin-created OAuth2 users.
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-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupCWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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 lookupCWE-521: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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 lookupCVE-2021-32753 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
- High
- CVSS
- 8.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L3.93.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.3HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/edgexfoundry/edgex-go/security/advisories/GHSA-xph4-vmcc-52ghCVE reference · x_refsource_CONFIRM
- https://docs.konghq.com/hub/kong-inc/oauth2/#create-a-consumerCVE 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.