Bug 159208 - CAN-2005-1267 tcpdump BGP DoS
Summary: CAN-2005-1267 tcpdump BGP DoS
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: tcpdump
Version: 4.0
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
: ---
Assignee: Martin Stransky
QA Contact:
URL:
Whiteboard: impact=low,source=vendorsec,reported=...
Keywords: Security
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-05-31 16:11 UTC by Josh Bressers
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2005-06-13 12:03:32 UTC


Attachments (Terms of Use)
Patch from upstream (423 bytes, patch)
2005-05-31 16:13 UTC, Josh Bressers
no flags Details | Diff
Proof of concept exploit (13.09 KB, text/plain)
2005-05-31 16:14 UTC, Josh Bressers
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:505 normal SHIPPED_LIVE Low: tcpdump security update 2005-06-13 04:00:00 UTC

Description Josh Bressers 2005-05-31 16:11:32 UTC
Simon L. Nielsen alerted vendor-sec to this issue:

While working on the FreeBSD Security Advisory for the recent tcpdump
issues (CAN-2005-1278, CAN-2005-1279, and CAN-2005-1280) I noticed
that there is another similar infinite loop DoS vulnerability in the
BGP handling code.

The problem lies in bgp_update_print() in print-bgp.c around line
1652, where the -1 return value from decode_prefix4() is not properly
handled.

This problem was fixed in tcpdump CVS repository in print-bgp.c
v. 1.95 on May 5, but it hasn't gone to the tcpdump 3.8 branch, and
hasn't been included in any of the vendor patch sets for earlier DoS
vulnerabilities that I have seen.

Comment 1 Josh Bressers 2005-05-31 16:12:22 UTC
This issue should also affect RHEL2.1 and RHEL3

Comment 2 Josh Bressers 2005-05-31 16:13:04 UTC
Created attachment 115005 [details]
Patch from upstream

Comment 3 Josh Bressers 2005-05-31 16:14:39 UTC
Created attachment 115006 [details]
Proof of concept exploit

Comment 4 Martin Stransky 2005-06-01 08:03:02 UTC
When will the embargo expire?

Comment 5 Josh Bressers 2005-06-01 11:24:41 UTC
There is no set date yet.  I'll let you know as soon as there is one.
 I expect it to be soon.  This fix is already in the upstream CVS, so
it makes little sense to try to keep it a secret for too long.

Comment 6 Mark J. Cox 2005-06-06 08:39:02 UTC
Removing embargo as per Simon Nielsen msg to vendor-sec

Comment 7 Martin Stransky 2005-06-08 08:34:20 UTC
RHEL2.1 and RHEL3 aren't affected by this issue, the bug is only in
version 3.8.2.

Comment 8 Josh Bressers 2005-06-13 12:03:32 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2005-505.html



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