github.com/edgexfoundry/app-service-configurable
View on Github
Activity
- Latest release
- 5y ago
- Total releases
- 20
- Cadence
- ~4 days
- Last 12 months
- 0
Reach
- Stars
- —
Details
- First release
- Sep 05, 2020
| Version | Released | |
|---|---|---|
v1.3.1-dev.3
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.3.1-dev.3
pre
Dependencies (1)
|
|
v1.3.1
patch
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.3.1
patch
Dependencies (1)
|
|
v1.3.1-dev.2
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.3.1-dev.2
pre
Dependencies (1)
|
|
v1.3.1-dev.1
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.3.1-dev.1
pre
Dependencies (1)
|
|
v1.2.1-dev.23
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.23
pre
Dependencies (1)
|
|
v1.3.0
initial
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.3.0
initial
Dependencies (1)
|
|
v1.2.1-dev.22
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.22
pre
Dependencies (1)
|
|
v1.2.1-dev.21
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.21
pre
Dependencies (1)
|
|
v1.2.1-dev.20
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.20
pre
Dependencies (1)
|
|
v1.2.1-dev.19
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.19
pre
Dependencies (1)
|
|
v1.2.1-dev.18
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.18
pre
Dependencies (1)
|
|
v1.2.1-dev.17
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.17
pre
Dependencies (1)
|
|
v1.2.1-dev.16
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.16
pre
Dependencies (1)
|
|
v1.2.1-dev.15
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.15
pre
Dependencies (1)
|
|
v1.2.1-dev.14
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.14
pre
Dependencies (1)
|
|
v1.2.1-dev.13
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.13
pre
Dependencies (1)
|
|
v1.2.1-dev.12
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.12
pre
Dependencies (1)
|
|
v1.2.1-dev.11
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.11
pre
Dependencies (1)
|
|
v1.2.1-dev.10
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.10
pre
Dependencies (1)
|
|
v1.2.1-dev.9
pre
1 CVE
CVE-2021-41278
GHSA-6c7m-qwxj-mvhp
Nov 19, 2021
Broken encryption in EdgeX Foundry
5.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
Low
None
SummaryBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. Detailed DescriptionThe 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. ImpactAs 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. Vulnerable go modules
Vulnerable containers
Vulnerable Snaps
PatchesUpgrade 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. Patched go modules
Modification of user scripts is necessary for full remediation. Patched containers
Modification of user scripts is necessary for full remediation. Patched Snaps
Modification of user scripts is necessary for full remediation. WorkaroundsIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption. ReferencesFor more informationIf you have any questions or comments about this advisory:
Fixed in
2.1.0
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.1-dev.9
pre
Dependencies (1)
|