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.042] OpenPKG Security Advisory (aspell)

Hash: SHA1


OpenPKG Security Advisory                            The OpenPKG Project                   
OpenPKG-SA-2004.042                                          15-Sep-2004

Package:             aspell
Vulnerability:       arbitrary code execution
OpenPKG Specific:    no

Affected Releases:   Affected Packages:        Corrected Packages:
OpenPKG CURRENT      <= aspell-0.50.5-20040310 >= aspell-0.60-20040827
OpenPKG 2.1          <= aspell-0.50.5-2.1.0    >= aspell-0.50.5-2.1.1
OpenPKG 2.0          <= aspell-0.50.5-2.0.0    >= aspell-0.50.5-2.0.1

Dependent Packages:  none

  According to a security advisory from shaun2k2 [0], multiple
  stack-based buffer overflows exists in the "word-list-compress"
  utility from the spell-checker GNU Aspell [1]. By providing a
  specially crafted word list containing an overly long string (more
  than 256 bytes), an attacker can cause a buffer overflow and execute
  arbitrary code. This allows an attacker to execute arbitrary code via
  a long entry in the wordlist. The Common Vulnerabilities and Exposures
  (CVE) project assigned the id CAN-2004-0548 [2] to the problem.

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

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

  $ ftp
  ftp> bin
  ftp> cd release/2.1/UPD
  ftp> get aspell-0.50.5-2.1.1.src.rpm
  ftp> bye
  $ <prefix>/bin/openpkg rpm -v --checksig aspell-0.50.5-2.1.1.src.rpm
  $ <prefix>/bin/openpkg rpm --rebuild aspell-0.50.5-2.1.1.src.rpm
  $ su -
  # <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/aspell-0.50.5-2.1.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