From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Fwd: Practical malleability attack against CBC-Encrypted LUKS partitions
Date: Mon, 23 Dec 2013 12:13:14 +0100 [thread overview]
Message-ID: <20131223111314.GC16429@tansi.org> (raw)
In-Reply-To: <20131222230724.GA1991@phobos.panopticism.net>
On Mon, Dec 23, 2013 at 00:07:24 CET, /dev/ph0b0s wrote:
> On 12/22, Milan Broz wrote:
> > Below is very nice example of another "Evil maid" type attacks,
> > here directly applied to LUKS CBC disks.
> >
> > I think it clearly shows known rule:
> > If you let your machine out of your sight, it is no longer your machine.
> >
> > What is important (and blog mentions it)
> >
> > "It has already been known for a long time that CBC does not prevent
> > a malleability attack (targeted manipulation of encrypted data) given
> > that the attacker can modify the ciphertext and knows the corresponding
> > plaintext as well."
>
> Even more important, in this particular case, is that this "practical
> malleability attack" isn't actually very practical at all:
>
> "In the following I assume that we already have access to the
> original plaintext and the ciphertext of one file on the system and
> that we want to do our manipulations in this file:"
>
> There are a number of other assumptions and variables that must be "just right"
> in order for this attack to have even a remote chance of working, e.g.:
>
> "This code can be executed from a Live CD against the encrypted
> partition of an Ubuntu 12.04 installation. The position of the
> /bin/dash file needs to be adjusted by doing a reference
> installation with the same disk layout on a sufficiently similar
> hardware."
And there lies a pretty catastrophic risk: If anything goes wrong,
the target will know it has been attacked. In many scenarios this
will prevent the use of this attack.
Arno
--
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
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult. --Tony Hoare
prev parent reply other threads:[~2013-12-23 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH8yC8=i5x0My2ZMJrj8oikE8t6vQUGUX8WP2PC1uhO6HS=Mbw@mail.gmail.com>
2013-12-22 22:06 ` [dm-crypt] Fwd: Practical malleability attack against CBC-Encrypted LUKS partitions Milan Broz
2013-12-22 23:07 ` /dev/ph0b0s
2013-12-23 7:56 ` Milan Broz
2013-12-23 11:13 ` 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=20131223111314.GC16429@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.