Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-58356: CWE-347: Improper Verification of Cryptographic Signature in edgelesssys constellation

0
High
VulnerabilityCVE-2025-58356cvecve-2025-58356cwe-347
Published: Mon Oct 27 2025 (10/27/2025, 19:33:23 UTC)
Source: CVE Database V5
Vendor/Project: edgelesssys
Product: constellation

Description

Constellation is the first Confidential Kubernetes. The Constellation CVM image uses LUKS2-encrypted volumes for persistent storage. When opening an encrypted storage device, the CVM uses the libcryptsetup function crypt_activate_by_passhrase. If the VM is successful in opening the partition with the disk encryption key, it treats the volume as confidential. However, due to the unsafe handling of null keyslot algorithms in the cryptsetup 2.8.1, it is possible that the opened volume is not encrypted at all. Cryptsetup prior to version 2.8.1 does not report an error when processing LUKS2-formatted disks that use the cipher_null-ecb algorithm in the keyslot encryption field. This vulnerability is fixed in 2.24.0.

AI-Powered Analysis

AILast updated: 11/28/2025, 22:35:00 UTC

Technical Analysis

CVE-2025-58356 is a vulnerability in edgelesssys Constellation, a Confidential Kubernetes platform that uses LUKS2-encrypted volumes for persistent storage. The Constellation CVM image relies on the libcryptsetup function crypt_activate_by_passphrase to open encrypted storage devices. However, cryptsetup versions prior to 2.8.1 do not properly handle the cipher_null-ecb algorithm in the keyslot encryption field of LUKS2 disks. This means that if an attacker configures a volume with this null cipher, cryptsetup may open the volume without error, even though it is not actually encrypted. Consequently, the system treats the volume as confidential while the data remains unencrypted and exposed. This improper verification of cryptographic signatures corresponds to CWE-347. The vulnerability compromises the confidentiality and integrity of data stored on these volumes. The issue is fixed in cryptsetup version 2.24.0. Exploitation requires local privileged access but no user interaction. No known exploits are currently in the wild. The vulnerability has a CVSS 4.0 score of 8.3, reflecting its high impact on confidentiality and integrity with relatively low attack complexity. This flaw undermines the core security guarantees of Confidential Kubernetes environments, potentially exposing sensitive workloads and data to unauthorized access.

Potential Impact

For European organizations deploying edgelesssys Constellation with vulnerable cryptsetup versions, this vulnerability poses a significant risk to the confidentiality and integrity of sensitive data stored on persistent volumes. Since Constellation is designed to provide confidential computing guarantees, the failure to properly verify encryption undermines trust in the platform's security. Attackers with local privileged access could exploit this flaw to access unencrypted data, leading to data breaches, intellectual property theft, or exposure of regulated information subject to GDPR. The impact is particularly critical for sectors handling sensitive data such as finance, healthcare, and government. Additionally, compromised confidentiality could facilitate further lateral movement or privilege escalation within Kubernetes clusters. The lack of user interaction required for exploitation and the high privileges needed limit the attack surface but do not eliminate risk, especially in multi-tenant or cloud environments where privileged access may be attainable. Overall, the vulnerability threatens the foundational security model of Confidential Kubernetes deployments in Europe.

Mitigation Recommendations

1. Immediately upgrade cryptsetup to version 2.24.0 or later on all systems running edgelesssys Constellation to ensure proper handling of LUKS2 volumes and keyslot encryption algorithms. 2. Audit existing encrypted volumes to detect any that use the cipher_null-ecb algorithm or other insecure keyslot configurations and re-encrypt them with secure algorithms. 3. Implement strict cryptographic policy enforcement to reject LUKS2 volumes with null or insecure cipher algorithms during creation or mounting. 4. Restrict local privileged access to trusted administrators and enforce strong access controls and monitoring to reduce the risk of exploitation. 5. Regularly monitor and verify the integrity and encryption status of persistent storage volumes within Kubernetes clusters. 6. Incorporate cryptographic validation checks into CI/CD pipelines and infrastructure as code to prevent deployment of vulnerable configurations. 7. Stay informed on vendor patches and security advisories related to edgelesssys Constellation and cryptsetup components. 8. Consider additional runtime security controls such as container security platforms that can detect anomalous volume mounts or access patterns.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-08-29T16:19:59.010Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68ffca08ba6dffc5e209fffc

Added to database: 10/27/2025, 7:37:44 PM

Last enriched: 11/28/2025, 10:35:00 PM

Last updated: 12/11/2025, 10:01:00 PM

Views: 176

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats