Bug 181836 - CVE-2006-0591 postgresql pgcrypt minor salt generation flaw
CVE-2006-0591 postgresql pgcrypt minor salt generation flaw
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rh-postgresql (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Tom Lane
: Security
Depends On:
  Show dependency treegraph
Reported: 2006-02-16 21:05 EST by Tom Lane
Modified: 2013-07-02 23:08 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-05-23 15:52:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tom Lane 2006-02-16 21:05:09 EST
+++ This bug was initially created as a clone of Bug #180536 +++

postgresql pgcrypt minor salt generation flaw


There is a signedness error in the way postgresql generated the
password salts.  Worst case scenario is there are only half as many
salts available as there should be.  This is only an issue if someone
can steal the hashed postgresql passwords, and even then it will still
take a VERY long time to crack these.  I don't know which algorithm we
use by default, but if it should take 2 weeks to crack, it will really
only take 1 week (probably longer).  Part of the problem with fixing
this is the already generated passwords are already weak, fixing this
will only affect new passwords..  Taking into account it's only
database passwords, I'm assigning this "low"

Here is the patch.


This issue also affects RHEL3

-- Additional comment from tgl@redhat.com on 2006-02-16 21:01 EST --
This has been fixed upstream in postgresql 7.4.11 (relevant to RHEL4) and 7.3.13 (relevant to RHEL3).  
There are a fair number of other serious bugs fixed in the upstream updates since we last turned 
postgresql in RHEL.  I think we ought to plan on pushing the updated versions out in the next quarterly 
update cycle.  This particular problem does not seem severe enough to justify an async security 
Comment 1 Tom Lane 2006-05-23 15:52:32 EDT
Fixed in postgresql 7.4.13 and 7.3.15, pushed today for other security errata.

Note You need to log in before you can comment on or make changes to this bug.