First published: Thu Sep 21 2023(Updated: )
On boot, the Pillar eve container checks for the existence and content of “/config/authorized_keys”. If the file is present, and contains a supported public key, the container will go on to open port 22 and enable sshd with the given keys as the authorized keys for root login. An attacker could easily add their own keys and gain full control over the system without triggering the “measured boot” mechanism implemented by EVE OS, and without marking the device as “UUD” (“Unknown Update Detected”). This is because the “/config” partition is not protected by “measured boot”, it is mutable, and it is not encrypted in any way. An attacker can gain full control over the device without changing the PCR values, thus not triggering the “measured boot” mechanism, and having full access to the vault. Note: This issue was partially fixed in these commits (after disclosure to Zededa), where the config partition measurement was added to PCR13: • aa3501d6c57206ced222c33aea15a9169d629141 • 5fef4d92e75838cc78010edaed5247dfbdae1889. This issue was made viable in version 9.0.0 when the calculation was moved to PCR14 but it was not included in the measured boot.
Credit: cve@asrg.io cve@asrg.io
Affected Software | Affected Version | How to fix |
---|---|---|
Linuxfoundation Edge Virtualization Engine | <8.6.0 | |
Linuxfoundation Edge Virtualization Engine | >=9.0.0<9.5.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-43631 refers to a vulnerability in the Pillar eve container that allows an attacker to unlock SSH as root without triggering measured boot.
The severity of CVE-2023-43631 is high, with a severity value of 8.8.
The Linuxfoundation Edge Virtualization Engine versions 8.6.0 up to exclusive 9.5.0 are affected by CVE-2023-43631.
CVE-2023-43631 exploits the presence and content of the '/config/authorized_keys' file in the Pillar eve container to enable root login via SSH without triggering measured boot.
Currently, there is no known fix for CVE-2023-43631. It is recommended to follow the provided reference for any updates or patches.