| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/edgexfoundry/app-functions-sdk-go | all versions | |
| github.com/edgexfoundry/app-functions-sdk-go/v2 | < 2.1.0 | 2.1.0 |
| github.com/edgexfoundry/app-service-configurable | < 2.1.0 | 2.1.0 |
| app service configurable | < 2.1.0 | 2.1.0 |
| application functions software development kit | < 2.1.0 | 2.1.0 |
| edgex foundry | < 2.1.0 | 2.1.0 |
Broken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors.
The app-functions-sdk exports an “aes” transform that user scripts can optionally call to encrypt data in the processing pipeline. No decrypt function is provided. Encryption is not enabled by default, but if used, the level of protection may be less than the user may expects due to a broken implementation in https://github.com/edgexfoundry/app-functions-sdk-go/blob/v1.0.0/pkg/transforms/encryption.go
Version v2.1.0 (EdgeX Foundry Jakarta release and later) of app-functions-sdk-go/v2 deprecates the “aes” transform and provides an improved “aes256” transform in its place. The broken implementation will remain in a deprecated state until it is removed in the next EdgeX major release to avoid breakage of existing software that depends on the broken implementation.
As the broken transform is a library function that is not invoked by default, users who do not use the AES transform in their processing pipelines are unaffected. Those that are affected are urged to upgrade to the Jakarta EdgeX release and modify processing pipelines to use the new "aes256" transform.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site freeUpgrade to 2.1.0 version of app-functions-sdk-go/v2, app-service-configurable, and related docker containers shown below and modify user scripts to use the new "aes256" transform in place of the existing "aes" transform.
Modification of user scripts is necessary for full remediation.
Modification of user scripts is necessary for full remediation.
Modification of user scripts is necessary for full remediation.
If unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption.
If you have any questions or comments about this advisory: