Impact

When the EdgeX API gateway is configured for OAuth2 authentication and a proxy user is created, the client_id and client_secret required to obtain an OAuth2 authentication token are set to the username of the proxy user. A remote network attacker can then perform a dictionary-based password attack on the OAuth2 token endpoint of the API gateway to obtain an OAuth2 authentication token and use that token to make authenticated calls to EdgeX microservices from an untrusted network.

OAuth2 is the default authentication method in EdgeX Edinburgh release. The default authentication method was changed to JWT in Fuji and later releases.

Patches

Users should upgrade to the EdgeX Ireland release to obtain the fix. The OAuth2 authentication method is disabled in Ireland release.

Workarounds

If unable to upgrade and OAuth2 authentication is required, users should create OAuth2 users directly using the Kong admin API and forgo the use of the security-proxy-setup tool to create OAuth2 users.

References

• Create an OAuth2 consumer directly using Kong API

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 EdgeX-TSC-Security@lists.edgexfoundry.org