Bug 152760

Summary: CAN-2004-0686 samba buffer overflow
Product: [Retired] Fedora Legacy Reporter: Marc Deslauriers <marc.deslauriers>
Component: Package requestAssignee: Fedora Legacy Bugs <bugs>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecified   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: https://rhn.redhat.com/errata/RHSA-2004-404.html
Whiteboard: LEGACY, rh73, rh90
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 David Lawrence 2005-03-30 23:26:30 UTC
Buffer overflow in Samba 2.2.x to 2.2.9, and 3.0.0 to 3.0.4, when the "mangling
method = hash" option is enabled in smb.conf, has unknown impact and attack vectors.

Info:
https://rhn.redhat.com/errata/RHSA-2004-404.html
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0686
http://marc.theaimsgroup.com/?l=bugtraq&m=109051340810458&w=2



------- Additional Comments From jp107.ac.uk 2004-08-05 04:25:13 ----

This seems to be a duplicate of #1924 ...




------- Additional Comments From marcdeslauriers 2004-08-05 13:04:40 ----

You're right. Bug 1924 didn't have the LEGACY keyword...

*** This bug has been marked as a duplicate of 1924 ***



------- Additional Comments From ville.skytta 2004-08-09 05:10:44 ----

Keyword cleanup for http://www.fedora.us/NEEDSWORK



------- Bug moved to this database by dkl 2005-03-30 18:26 -------

This bug previously known as bug 1946 at https://bugzilla.fedora.us/
https://bugzilla.fedora.us/show_bug.cgi?id=1946
Originally filed under the Fedora Legacy product and Package request component.

Unknown priority P2. Setting to default priority "normal".
Unknown platform PC. Setting to default platform "All".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.