From owner-freebsd-security@freebsd.org  Fri Jan  5 12:42:55 2018
Return-Path: <owner-freebsd-security@freebsd.org>
Delivered-To: freebsd-security@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0D1AEA6BA7;
 Fri,  5 Jan 2018 12:42:55 +0000 (UTC)
 (envelope-from eric@metricspace.net)
Received: from mail.metricspace.net (mail.metricspace.net
 [IPv6:2001:470:1f11:617::107])
 by mx1.freebsd.org (Postfix) with ESMTP id C44D8670C3;
 Fri,  5 Jan 2018 12:42:55 +0000 (UTC)
 (envelope-from eric@metricspace.net)
Received: from [172.16.0.82] (unknown [172.16.0.82])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate) (Authenticated sender: eric)
 by mail.metricspace.net (Postfix) with ESMTPSA id 3ED298850;
 Fri,  5 Jan 2018 12:42:54 +0000 (UTC)
Subject: Re: Intel hardware bug
To: Jules Gilbert <repeatable_compression@yahoo.com>,
 "Ronald F. Guilmette" <rfg@tristatelogic.com>,
 Freebsd Security <freebsd-security@freebsd.org>,
 Brett Glass <brett@lariat.org>, =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?=
 <des@des.no>, Poul-Henning Kamp <phk@phk.freebsd.dk>,
 "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>,
 FreeBSD Hackers <freebsd-hackers@freebsd.org>,
 Shawn Webb <shawn.webb@hardenedbsd.org>,
 Nathan Whitehorn <nwhitehorn@freebsd.org>
References: <736a2b77-d4a0-b03f-8a6b-6a717f5744d4@metricspace.net>
 <2594.1515141192@segfault.tristatelogic.com>
 <809675000.867372.1515146821354@mail.yahoo.com>
From: Eric McCorkle <eric@metricspace.net>
Message-ID: <250f3a77-822b-fba5-dcd7-758dfec94554@metricspace.net>
Date: Fri, 5 Jan 2018 07:42:53 -0500
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <809675000.867372.1515146821354@mail.yahoo.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 05 Jan 2018 12:49:00 +0000
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jan 2018 12:42:56 -0000

On 01/05/2018 05:07, Jules Gilbert wrote:
> Sorry guys, you just convinced me that no one, not the NSA, not the FSB,
> no one!, has in the past, or will in the future be able to exploit this
> to actually do something not nice.

Attacks have already been demonstrated, pulling secrets out of kernel
space with meltdown and http headers/passwords out of a browser with
spectre.  Javascript PoCs are already in existence, and we can expect
them to find their way into adware-based malware within a week or two.

Also, I'd be willing to bet you a year's rent that certain three-letter
organizations have known about and used this for some time.

> So what is this, really?, it's a market exploit opportunity for AMD.

Don't bet on it.  There's reports of AMD vulnerabilities, also for ARM.
I doubt any major architecture is going to make it out unscathed.  (But
if one does, my money's on Power)