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  linux-hardening  linux-cve-announce  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]
Date: Fri, 28 Nov 2003 13:22:41 +0100
From: OpenPKG <>
Subject: [OpenPKG-SA-2003.050] OpenPKG Security Advisory (screen)

Hash: SHA1


OpenPKG Security Advisory                            The OpenPKG Project                   
OpenPKG-SA-2003.050                                          28-Nov-2003

Package:             screen
Vulnerability:       privilege escalation
OpenPKG Specific:    no

Affected Releases:   Affected Packages:          Corrected Packages:
OpenPKG CURRENT      <= screen-4.0.1-20031009    >= screen-4.0.1-20031127
OpenPKG 1.3          <= screen-3.9.15-1.3.0      >= screen-3.9.15-1.3.1
OpenPKG 1.2          <= screen-3.9.13-1.2.0      >= screen-3.9.13-1.2.1

Dependent Packages:  none

  Timo Sirainen reported and fixed [1] a buffer overflow bug which
  allows privilege escalation in the Virtual Screen Manager GNU screen
  [2], whose executable is installed setuid-root. It also has some
  potential for attackers getting control of another user's screen.
  Transfer of approximately two gigabytes of data is required to exploit
  this vulnerability.

  Please check whether you are affected by running "<prefix>/bin/rpm -q
  screen". If you have the "screen" package installed and its version
  is affected (see above), we recommend that you immediately upgrade it
  (see Solution). [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 current release OpenPKG 1.3, perform the
  following operations to permanently fix the security problem (for
  other releases adjust accordingly).

  $ ftp
  ftp> bin
  ftp> cd release/1.3/UPD
  ftp> get screen-3.9.15-1.3.1.src.rpm
  ftp> bye
  $ <prefix>/bin/rpm -v --checksig screen-3.9.15-1.3.1.src.rpm
  $ <prefix>/bin/rpm --rebuild screen-3.9.15-1.3.1.src.rpm
  $ su -
  # <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/screen-3.9.15-1.3.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