Skip to content
Fencer Vulns
medium 5.4

CVE-2021-41278 json

Broken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors

published 2021-11-18 4 y ago modified 2026-07-08 4 mo ago also GHSA-6c7m-qwxj-mvhp , EUVD-2021-2305

cvss
5.4
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

Functions SDK for EdgeX is meant to provide all the plumbing necessary for developers to get started in processing/transforming/exporting data out of the EdgeX IoT platform. In affected versions 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. 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.

Patch / fix

  • go github.com/edgexfoundry/app-functions-sdk-go/v2 2.1.0
  • go github.com/edgexfoundry/app-service-configurable 2.1.0
  • edgexfoundry app_service_configurable 2.1.0
  • edgexfoundry application_functions_software_development_kit 2.1.0
  • edgexfoundry edgex_foundry 2.1.0

Exploit prediction

0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.0 5.4 CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N
NVD 3.1 5.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
NVD 2.0 2.6 AV:N/AC:H/Au:N/C:P/I:N/A:N
GitHub 3.0 5.4 CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/edgexfoundry/app-functions-sdk-go/v2
<2.1.0
2.1.0
go github.com/edgexfoundry/app-functions-sdk-go
all versions
 no fix listed
go github.com/edgexfoundry/app-service-configurable
<2.1.0
2.1.0

Affected products

  • edgexfoundry app-functions-sdk-go

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.