lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
From: openpkg at (OpenPKG)
Subject: [OpenPKG-SA-2004.010] OpenPKG Security Advisory (tcpdump)

Hash: SHA1


OpenPKG Security Advisory                            The OpenPKG Project                   
OpenPKG-SA-2004.010                                          07-Apr-2004

Package:             tcpdump
Vulnerability:       denial of service
OpenPKG Specific:    no

Affected Releases:   Affected Packages:          Corrected Packages:
OpenPKG CURRENT      <= tcpdump-3.8.1-20040207   >= tcpdump-3.8.2-20040330
OpenPKG 2.0          <= tcpdump-3.8.1-2.0.0      >= tcpdump-3.8.1-2.0.1
OpenPKG 1.3          <= tcpdump-3.7.2-1.3.1      >= tcpdump-3.7.2-1.3.2

Dependent Packages:  none

  According to a security advisory published by Rapid7 [0], two
  vulnerabilities exists in the ISAKMP packet display functions of
  tcpdump [1]. The Common Vulnerabilities and Exposures (CVE) project
  has reviewed both problems. CAN-2004-0183 [2] identifies an overflow
  when displaying ISAKMP delete payloads with large number of SPIs,
  while CAN-2004-0184 [3] identifies an integer underflow when
  displaying ISAKMP identification payload. These vulnerabilities
  appear only when verbose packet display is enabled by running tcpdump
  with the -v option.

  Please check whether you are affected by running "<prefix>/bin/rpm
  -q tcpdump". If you have the "tcpdump" package installed and its
  version is affected (see above), we recommend that you immediately
  upgrade it (see Solution). [4][5]

  Select the updated source RPM appropriate for your OpenPKG release
  [6][7], fetch it from the OpenPKG FTP service [8][9] or a mirror
  location, verify its integrity [10], build a corresponding binary RPM
  from it [4] and update your OpenPKG installation by applying the
  binary RPM [5]. For the most current release OpenPKG 2.0, perform the
  following operations to permanently fix the security problem (for
  other releases adjust accordingly).

  $ ftp
  ftp> bin
  ftp> cd release/2.0/UPD
  ftp> get tcpdump-3.8.1-2.0.1.src.rpm
  ftp> bye
  $ <prefix>/bin/rpm -v --checksig tcpdump-3.8.1-2.0.1.src.rpm
  $ <prefix>/bin/rpm --rebuild tcpdump-3.8.1-2.0.1.src.rpm
  $ su -
  # <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/tcpdump-3.8.1-2.0.1.*.rpm


For security reasons, this advisory was digitally signed with the
OpenPGP public key "OpenPKG <>" (ID 63C4CB9F) of the
OpenPKG project which you can retrieve from and
hkp:// Follow the instructions on
for details on how to verify the integrity of this advisory.

Comment: OpenPKG <>


Powered by blists - more mailing lists