-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ________________________________________________________________________ OpenPKG Security Advisory The OpenPKG Project http://www.openpkg.org/security.html http://www.openpkg.org firstname.lastname@example.org email@example.com OpenPKG-SA-2004.024 19-May-2004 ________________________________________________________________________ Package: neon, subversion, cadaver, sitecopy, tla Vulnerability: remote code execution OpenPKG Specific: no Affected Releases: Affected Packages: Corrected Packages: OpenPKG CURRENT <= neon-0.24.5-20040414 >= neon-0.24.6-20040519 <= subversion-1.0.2-20040518 >= subversion-1.0.3-20040519 <= cadaver-0.22.1-20040415 >= cadaver-0.22.2-20040519 <= sitecopy-0.13.4-20040416 >= sitecopy-0.13.4-20040519 <= tla-1.2-20040416 >= tla-1.2-20040519 OpenPKG 2.0 <= neon-0.24.4-2.0.1 >= neon-0.24.4-2.0.2 <= subversion-1.0.0-2.0.1 >= subversion-1.0.0-2.0.2 <= cadaver-0.22.0-2.0.1 >= cadaver-0.22.0-2.0.2 <= sitecopy-0.13.4-2.0.1 >= sitecopy-0.13.4-2.0.2 OpenPKG 1.3 <= neon-0.24.0-1.3.1 >= neon-0.24.0-1.3.2 <= sitecopy-0.13.3-1.3.1 >= sitecopy-0.13.3-1.3.2 Dependent Packages: none Description: Stefan Esser discovered  a vulnerability within a date parsing function in the Neon HTTP and WebDAV client library . If a special crafted date string is passed to the ne_rfc1036_parse() function it may trigger a sscanf() string overflow into static heap variables. Exploitability heavily depends on the application linked against Neon, but is considered trivial in cases where an out-of-memory condition can be triggered, because the overflowing variable is placed in front of the Neon out-of-memory callback function pointer. The Common Vulnerabilities and Exposures (CVE) project assigned the id CAN-2004-0398  to the problem. Please check whether you are affected by running "
/bin/rpm -q neon" (respectively for "subversion", "cadaver", "sitecopy" and "tla"). If you have one of the packages installed and its version is affected (see above), we recommend that you immediately upgrade it (see Solution) . Solution: Select the updated source RPM appropriate for your OpenPKG release , fetch it from the OpenPKG FTP service  or a mirror location, verify its integrity , build a corresponding binary RPM from it  and update your OpenPKG installation by applying the binary RPM . For the most recent release OpenPKG 2.0, perform the following operations to permanently fix the security problem (for other releases adjust accordingly). $ ftp ftp.openpkg.org ftp> bin ftp> cd release/2.0/UPD ftp> get neon-0.24.4-2.0.2.src.rpm ftp> bye $ /bin/openpkg rpm -v --checksig neon-0.24.4-2.0.2.src.rpm $ /bin/openpkg rpm --rebuild neon-0.24.4-2.0.2.src.rpm $ su - # /bin/openpkg rpm -Fvh /RPM/PKG/neon-0.24.4-2.0.2.*.rpm Additionally, perform similar steps for the "subversion", "cadaver", "sitecopy" and "tla" packages. ________________________________________________________________________ References:  http://www.webdav.org/neon/  http://security.e-matters.de/advisories/062004.html  http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0398  http://www.openpkg.org/tutorial.html#regular-source  http://www.openpkg.org/tutorial.html#regular-binary  ftp://ftp.openpkg.org/release/1.3/UPD/neon-0.24.0-1.3.2.src.rpm  ftp://ftp.openpkg.org/release/1.3/UPD/sitecopy-0.13.3-1.3.2.src.rpm  ftp://ftp.openpkg.org/release/2.0/UPD/neon-0.24.4-2.0.2.src.rpm  ftp://ftp.openpkg.org/release/2.0/UPD/subversion-1.0.0-2.0.2.src.rpm  ftp://ftp.openpkg.org/release/2.0/UPD/cadaver-0.22.0-2.0.2.src.rpm  ftp://ftp.openpkg.org/release/2.0/UPD/sitecopy-0.13.4-2.0.2.src.rpm  ftp://ftp.openpkg.org/release/1.3/UPD/  ftp://ftp.openpkg.org/release/2.0/UPD/  http://www.openpkg.org/security.html#signature ________________________________________________________________________ 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 http://pgp.openpkg.org and hkp://pgp.openpkg.org. Follow the instructions on http://pgp.openpkg.org/ for details on how to verify the integrity of this advisory. ________________________________________________________________________ -----BEGIN PGP SIGNATURE----- Comment: OpenPKG iD8DBQFAq8mzgHWT4GPEy58RAt4UAJ9Rmkb2p8hUofMJK4D9WdDOvBnUegCgknv5 lfvBQWamox0hDjNA4Wa/uB8= =fVnD -----END PGP SIGNATURE-----