[dm-crypt] About CVE-2016-4484: - Cryptsetup Initrd root Shell
arno at wagner.name
Tue Nov 15 14:27:57 CET 2016
Interesting. Does not very seem relevant, except in special
situations, where an attacker can boot the system and can
access the console, but cannot change the boot-process
or boot image itself.
This would immediately exclude any normal PC
from consideration, because there, if you can boot,
you can also boot something else which gives you the
same capabilities (or better) than this exploit.
If you can get BIOS access, the same might be possible,
so servers with ILO should also not be affected.
My take would be that of this vulnerabilituy allowas
an attack, then the security model used is broken in
the first place. Of course, there are environments that
need two (or more) effective security mechanisms, so
fixing this is a good idea, but (almost) nobody needs
to be very concerned about it.
On Tue, Nov 15, 2016 at 13:34:49 CET, Milan Broz wrote:
> Hi all,
> just little bit clarification about CVE-2016-4484
> This bug is *NOT* cryptsetup/LUKS upstream bug, it is a minor problem in scripts
> unlocking an encrypted system.
> It allows attacker to drop to initramdisk shell (without decryption of LUKS data).
> The scripts are part of Debian cryptsetup package (as an addition to upstream)
> or part of dracut package (if dracut is used).
> (The info about the problem was embargoed until the talk and only Debian maintainers
> were informed in advance.)
> dm-crypt mailing list
> dm-crypt at saout.de
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno at wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
More information about the dm-crypt