Message decryption via fixed unauthenticated CBC encryption
Published Nov 18, 2021 · Updated Aug 4, 2024
Broken encryption in EdgeX Foundry Application Functions SDK for Go before 2.1.0 allows attackers to decrypt pipeline messages. The optional EncryptWithAES transform truncates a SHA-1 digest into a 128-bit AES key, reuses a configured IV for CBC encryption, and adds no authentication tag. Only applications that invoke the AES transform in a processing pipeline are exposed, weakening the confidentiality and integrity of protected messages.
Summary
What happened
Broken encryption in EdgeX Foundry Application Functions SDK for Go before 2.1.0 allows attackers to decrypt pipeline messages. The optional EncryptWithAES transform truncates a SHA-1 digest into a 128-bit AES key, reuses a configured IV for CBC encryption, and adds no authentication tag. Only applications that invoke the AES transform in a processing pipeline are exposed, weakening the confidentiality and integrity of protected messages.
The record
- CVE
- CVE-2021-41278
- Published
- Nov 18, 2021
- Updated
- Aug 4, 2024
- Vendor
- EdgeX Foundry
- Product
- Application Functions SDK for Go
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 18, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo