Bug 151434 - Buffer overflow in cracklib
Summary: Buffer overflow in cracklib
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: cracklib
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Brian Brock
URL: http://sourceforge.net/mailarchive/fo...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-17 20:55 UTC by Jürgen Hötzel
Modified: 2008-01-05 17:40 UTC (History)
1 user (show)

Fixed In Version: cracklib-2.8.9-10
Clone Of:
Environment:
Last Closed: 2008-01-05 17:40:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jürgen Hötzel 2005-03-17 20:55:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Description of problem:
Buffer overflow in cracklib (verified 2.8.x and 2.7). This could lead to
execution of arbitrary code when not using stack smashing protection:
 
exploited in C:
 
FascistCheck(pwd, string_longer_than_1024_bytes);
-> Speicherzugriffsfehler (core dumped)
 
or PHP (crack extension must be loaded):
 
<?PHP
$foo =  sprintf("%2048s", "foo");
$dictionary = crack_opendict($foo) or die("Unable to open CrackLib dictionary");
?>
-> child pid 16256 exit signal Segmentation fault (11)
 

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
See description.
Supply dictionary > 1024 as user input
  

Additional info:

Comment 1 Matthew Miller 2006-07-10 21:36:47 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!


Comment 2 Till Maas 2008-01-05 17:40:39 UTC
I get "File name too long" with cracklib-2.8.9-10 from Fedora 7


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