From owner-freebsd-security@FreeBSD.ORG  Thu Sep 12 00:15:11 2013
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id E5452D54
 for <freebsd-security@FreeBSD.org>; Thu, 12 Sep 2013 00:15:11 +0000 (UTC)
 (envelope-from jonathon.s.wright@gmail.com)
Received: from mail-vc0-x235.google.com (mail-vc0-x235.google.com
 [IPv6:2607:f8b0:400c:c03::235])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id A8DB8222D
 for <freebsd-security@FreeBSD.org>; Thu, 12 Sep 2013 00:15:11 +0000 (UTC)
Received: by mail-vc0-f181.google.com with SMTP id hz10so6615513vcb.26
 for <freebsd-security@FreeBSD.org>; Wed, 11 Sep 2013 17:15:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=Ub2s43Vo7fl04jpnThi1erBJO1Ae4lcEIQz+NhsGUbE=;
 b=NYKymiMBoYewGNWch43m17to0+t5qrqwOHdW39StsIasYIZttzaMuROBVuIPhiU1Sz
 e4GdcURZ/LzC0v4ApQZa9X/iV7hwVJVhjlhcisk70Cm60+CoX+2dXZ+zEru60p/qH/s2
 dNDUKTQ75MjK8VNj5rjoSAuGLKgx6Zyp9+SZjpF4RWmvDvn+v8Mrqx4fiibj4iol0HNh
 gwQi4Ipvthb7a1ei81Nd90qwvllK2bB/TZh2JHy3puX1lPTOR6NwBJd7AkdEqdT7kJW5
 qo0GI7NkNsPl3LB8FfuHR/6FdWvcvxxXlZ9dX3zYL0hYUMbwHmnSq7KbfnrwhMeu+Bjb
 bajQ==
MIME-Version: 1.0
X-Received: by 10.52.114.231 with SMTP id jj7mr3257350vdb.2.1378944910757;
 Wed, 11 Sep 2013 17:15:10 -0700 (PDT)
Received: by 10.58.41.66 with HTTP; Wed, 11 Sep 2013 17:15:10 -0700 (PDT)
Date: Wed, 11 Sep 2013 14:15:10 -1000
Message-ID: <CAGX1DMbQP=TggYQm-3hra0Od3gjgz5xQ8bEMMrueuhL6kuZMUA@mail.gmail.com>
Subject: FreeBSD Transient Memory problem?
From: Jonathon Wright <jonathon.s.wright@gmail.com>
To: freebsd-security@FreeBSD.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Sep 2013 00:15:12 -0000

All,

I have posted this question (username-scryptkiddy) in the forums:
http://forums.freebsd.org/showthread.php?t=41875
but was suggested to bring it here to the mailing list for discussion.

Basically, FreeBSD 8.3 (64bit) is what we use in our shop. We were
inspected by a security team and they had issues with FreeBSD's memory
management.

Namely the transient memory and object reuse areas of FreeBSD. They claimed
that FreeBSD did not have a Common Criteria (EAL1-4) evaluation completed,
and therefore was vulnerable to the Transient memory problem.

Our higher ups need some sort of documentation / testing  that can be used
to counter this, since changing Operating Systems is not something we have
time / manpower to do, but might have too based on this supposed 'finding'.

The post has all the details. Let me know I need to repost in this as well.

JW