Bug 180537

Summary: CVE-2006-0591 postgresql pgcrypt minor salt generation flaw
Product: [Fedora] Fedora Reporter: Josh Bressers <bressers>
Component: postgresqlAssignee: Tom Lane <tgl>
Status: CLOSED CURRENTRELEASE QA Contact: David Lawrence <dkl>
Severity: low Docs Contact:
Priority: medium    
Version: 4CC: hhorak
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: impact=low,public=20060207,reported=20060105,source=vendor-sec
Fixed In Version: postgresql-8.0.6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-17 01:50:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Josh Bressers 2006-02-08 20:49:48 UTC
postgresql pgcrypt minor salt generation flaw

http://marc.theaimsgroup.com/?l=bugtraq&m=113933370118193&w=2

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.

http://cvsweb.openwall.com/cgi/cvsweb.cgi/Owl/packages/glibc/crypt_blowfish/crypt_gensalt.c.diff?r1=1.1;r2=1.2

Comment 1 Tom Lane 2006-02-17 01:50:38 UTC
This is fixed in Postgres 8.0.6, which we pushed to fc4 a month ago.