bugtraq - Re: Demarc Puresecure v1.6 - Plaintext password issue -

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <009601c32210$d64fa1f0$1500020a@bigdog>
Date: Sat, 24 May 2003 09:23:40 -0700
From: "Kurt Seifried" <kurt@...fried.org>
To: "David Barroso" <dbarroso@...sec.com>,
	"Ryan Purita" <ryan@...ally-connected.com>
Subject: Re: Demarc Puresecure v1.6 - Plaintext password issue -

>"Ryan Purita" <ryan@...ally-connected.com> wrote:

>The file psd.conf should be owned by root and its mode 600. Only if a
person gets root access in that box, she could read the password. Lots of
applications relay on that, for instance, snort, which is used by Demarc
PureSecure, stores the SQL password in plain text in snort.conf.

-------

But why do the agents need "DROP" privileges on the database? In my mind for
any "secure" logging system the agents should have append only access, that
is the ability to create new entries. Not modify or remove old ones. If an
attacker breaks into a Puresecure agent they can now flush out any traces of
their attack and future attacks on the server. Seeing as how this product is
aimed at major deployment (i.e. multiple sensors) including installation on
end systems (running all sorts of potentially vulnerable services, or simply
having hostile users with local access already....) this creates a huge
number of oppurtunities for an attacker.

Is it just me or does anyone else think such as system where the agents have
the ability to remove any trace of an attack once they are compromised is a
bad thing?

Kurt Seifried, kurt@...fried.org
A15B BEE5 B391 B9AD B0EF
AEB0 AD63 0B4E AD56 E574
http://seifried.org/security/