From owner-freebsd-security@freebsd.org Wed Mar 22 23:12:38 2017 Return-Path: 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 746AFD18C01; Wed, 22 Mar 2017 23:12:38 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-vk0-x244.google.com (mail-vk0-x244.google.com [IPv6:2607:f8b0:400c:c05::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FC0317C0; Wed, 22 Mar 2017 23:12:38 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by mail-vk0-x244.google.com with SMTP id j64so17376253vkg.0; Wed, 22 Mar 2017 16:12:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=J4yAAyNGmVYThYlbDvizeJDSZR5kVFHNArcr3ArW2dE=; b=cCNZTAZr+miW4WCw12CgeCa6gr/86/LehyriCtiSWi5fDPvzoY7rsY7xSwuJTLbuMV lQau7ooK8pEkXzyspVu19WYbrVUVvljj5uT2O4zEtZOSo0iSfCdvR68m7mTC+bEul/3z iU1TJ8S87RRhRXzQoWxYmX+vUlrS1UFAOlHtKOSyIrwXq2nTA1LJc/VH1+UA15TIbXRB k31EAr9F/ehvcyEOc0jqzPI+Vb1m/dA0jv1ClGVisXSzh72J0Axyn9218HjlQAkDcXVl M1I3lSRLPx74duJqhXGa9G/gT4NvF4wmhdMrElW7i3f3COpb/pFHl5FF0YrjoLZRVisD uWtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=J4yAAyNGmVYThYlbDvizeJDSZR5kVFHNArcr3ArW2dE=; b=steE8h4bRgqjRsrN1QxDmZIiNNMEuh7tLiu5Bd9vePKRpSJponQ2qAKYvcPmxSSipF LHx3jk39B7XZSI1cY05wDTge1DG3SQwKz/meuVIdbuX8JXLdBYtjA0ooEMga/d7LhKOK sjwdC6r5EmtWn3xKsAiJC6BLMnSe84DXX/VOvLafurPeOJonD690+3g0VbuN5ZPi5crM V0lqS5fHDouaNAMDXKTln7n1Jvuca3a0Y7mhB+ExcrPbdbqzWKvUzLcoTxxPezEaCUsN vY/l6GAUeJSt2gFq6WT7Vv+IjCnKXEh5mdOsyJo6PvxH6KSZKenTL2ApaxAttz1ehBaZ R2ZA== X-Gm-Message-State: AFeK/H1Nok8Gx8kU5gWUkkY7gwcrbXtCSvWXGOqgr5bZ/BziCIbW7dE5Iz/RNDCHi8ML20uUZjspjmsr2RxlzQ== X-Received: by 10.176.91.87 with SMTP id v23mr15252195uae.90.1490224356990; Wed, 22 Mar 2017 16:12:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.159.33.37 with HTTP; Wed, 22 Mar 2017 16:11:56 -0700 (PDT) In-Reply-To: References: From: grarpamp Date: Wed, 22 Mar 2017 19:11:56 -0400 Message-ID: Subject: Re: Filtering Against Persistent Firmware Rootkits - BadUSB, HDDHack, UEFI To: freebsd-security@freebsd.org Cc: freebsd-hardware@freebsd.org, freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Thu, 23 Mar 2017 12:30:15 +0000 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Mar 2017 23:12:38 -0000 > It is virtually impossible to guard against firmware rootkits because > cpu cannot prevent the card's or device's cpu from from executing that code. > This was made known by the malware embedded in disk drives' FW, and > other peripherals' FW, such as wifi and graphics, to name a couple. > It is possible for such device FW to insert malware into, > or modify, the RAM resident OS. > Apparently making OS's executable segments "non-writeable" can be gotten > around. There are two very different write directions involved... HW -> OS / SW ... Yes, as above, you're screwed. SW -> OS -> HW ... However, as before, you can add kernel filters to further help prevent software from writing the screwed firmware to your hardware in the first place.