Bug 86315 - updated tcpdump 3.7.2 and libcap 0.7.2 not available via RHN
updated tcpdump 3.7.2 and libcap 0.7.2 not available via RHN
Status: CLOSED DUPLICATE of bug 81585
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Other (Show other bugs)
RHN Stable
All Linux
medium Severity high
: ---
: ---
Assigned To: Chip Turner
Red Hat Satellite QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-19 10:31 EST by Mike Harris
Modified: 2007-04-18 12:52 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:52:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mike Harris 2003-03-19 10:31:18 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; UMHC IEAK 6 
2002; .NET CLR 1.0.3705)

Description of problem:
updates for Tcpdump 3.7.2 and Libcap 0.7.2 are not available via RHN and 
automated patching service.

see critical malformmed RADIUS packet denial of service vulnerability 
http://www.securityfocus.com/bid/7090

users of ids products using tcpdump and tcpdump feeds to snort are experiencing 
denial of service by tcpdump filling the hard disk with "0#0#0#0#" when these 
crafted packets hit tcpdump

manual update using updates from http://www.tcpdump.org seem to work but 
prevent future update via rhn as manually modified code
 

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


How reproducible:
Always

Steps to Reproduce:
1.n/a patches exsist but are unavailable via rhn
2.
3.
    

Additional info:
Comment 1 Mark J. Cox (Product Security) 2003-03-19 10:56:56 EST

*** This bug has been marked as a duplicate of 81585 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:52:14 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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