Constellation
Approved changes feed: RSS · Atom
cpe:2.3:a:edgelesssys:constellation:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Edgelesssys (55fb87da-b922-596e-8f45-e6af325b00a1) |
|---|---|
| Product | Constellation (eee1ab57-4aa4-5e76-8b24-670be67c0e3d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-58356 |
vulnerable | 2026-06-08 07:35:18.032874 |
Constellation allows insecure use of LUKS2 persistent storage partitions
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.
Published: 2025-10-27T19:33:23.969Z
Updated: 2025-11-28T14:45:46.203Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.