From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] About CVE-2016-4484: - Cryptsetup Initrd root Shell
Date: Wed, 7 Dec 2016 14:00:12 +0100 [thread overview]
Message-ID: <20161207130012.GA5078@tansi.org> (raw)
In-Reply-To: <b106b33a-e1d4-49cd-17ac-af316482c6b6@freesources.org>
Hi Jonas,
one thing I find particularly telling is that CVE-2016-4484
is still unpublished and there is only a placeholder:
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4484
This rather strongly indicates to me that this was all about
publicity and not about security at all. If they cannot
even be bothered to have that CVE actually out some 20 days
after making a splash at a conference and hyping it to the
press, this cannot be of any importance, security-wise...
Regards,
Arno
On Wed, Dec 07, 2016 at 12:37:04 CET, Jonas Meurer wrote:
> Hi there,
>
> Am 15.11.2016 um 13:34 schrieb Milan Broz:
> > just little bit clarification about CVE-2016-4484
> > http://hmarco.org/bugs/CVE-2016-4484/CVE-2016-4484_cryptsetup_initrd_shell.html
> >
> > 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).
>
> I decided to write down my thoughts on CVE-2016-4484 and published them
> in a blog post:
>
> https://blog.freesources.org/posts/2016/12/CVE-2016-4484/
>
> Feel free to share your comments, criticism, opinion either in the blog
> comments or here on the list.
>
> Cheers,
> jonas
>
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@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
prev parent reply other threads:[~2016-12-07 13:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 12:34 [dm-crypt] About CVE-2016-4484: - Cryptsetup Initrd root Shell Milan Broz
2016-11-15 13:27 ` Arno Wagner
2016-11-15 13:32 ` Sven Eschenberg
2016-11-15 15:18 ` Robert Nichols
2016-11-15 18:40 ` Sven Eschenberg
2016-11-15 19:19 ` Robert Nichols
2016-11-15 19:42 ` Sven Eschenberg
2016-11-15 22:51 ` Robert Nichols
2016-11-15 23:15 ` Michael Kjörling
2016-11-15 23:28 ` Sven Eschenberg
2016-11-15 23:52 ` Arno Wagner
2016-11-16 0:08 ` Jonas Meurer
2016-11-16 1:15 ` Sven Eschenberg
2016-11-16 7:32 ` Milan Broz
2016-11-16 13:48 ` Arno Wagner
2016-11-29 14:56 ` David Niklas
2016-12-07 11:37 ` Jonas Meurer
2016-12-07 13:00 ` Arno Wagner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161207130012.GA5078@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox