Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 159208 - CAN-2005-1267 tcpdump BGP DoS
CAN-2005-1267 tcpdump BGP DoS
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: tcpdump (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Martin Stransky
: Security
Depends On:
  Show dependency treegraph
Reported: 2005-05-31 12:11 EDT by Josh Bressers
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version: RHSA-2005-505
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-13 08:03:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch from upstream (423 bytes, patch)
2005-05-31 12:13 EDT, Josh Bressers
no flags Details | Diff
Proof of concept exploit (13.09 KB, text/plain)
2005-05-31 12:14 EDT, 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 00:00:00 EDT

  None (edit)
Description Josh Bressers 2005-05-31 12:11:32 EDT
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

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 12:12:22 EDT
This issue should also affect RHEL2.1 and RHEL3
Comment 2 Josh Bressers 2005-05-31 12:13:04 EDT
Created attachment 115005 [details]
Patch from upstream
Comment 3 Josh Bressers 2005-05-31 12:14:39 EDT
Created attachment 115006 [details]
Proof of concept exploit
Comment 4 Martin Stransky 2005-06-01 04:03:02 EDT
When will the embargo expire?
Comment 5 Josh Bressers 2005-06-01 07:24:41 EDT
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 04:39:02 EDT
Removing embargo as per Simon Nielsen msg to vendor-sec
Comment 7 Martin Stransky 2005-06-08 04:34:20 EDT
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 08:03:32 EDT
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.


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