[Security Announce] MDKSA-2003:018 - Updated apcupsd packages fix buffer overflow and remove vulnerability From: Mandrake Linux Security Team <security@linux-mandrake.com> To: security-announce@linux-mandrake.com Date: Today 00.05.37 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ________________________________________________________________________ Mandrake Linux Security Update Advisory ________________________________________________________________________ Package name: apcupsd Advisory ID: MDKSA-2003:018 Date: February 18th, 2003 Affected versions: 8.1, 8.2, 9.0 ________________________________________________________________________ Problem Description: A remote root vulnerability in slave setups and some buffer overflows in the network information server code were discovered by the apcupsd developers. They have been fixed in the latest unstable version, 3.10.5 which contains additional enhancements like USB support, and the latest stable version, 3.8.6. There are a few changes that need to be noted, such as the port has changed from port 7000 to post 3551 for NIS, and the new config only allows access from the localhost. Users may need to modify their configuration files appropriately, depending upon their configuration. ________________________________________________________________________ References: ________________________________________________________________________ Updated Packages: Mandrake Linux 8.1: fe8b89884f11d6ee419e791e7c7ff76e 8.1/RPMS/apcupsd-3.10.5-1.1mdk.i586.rpm cf73f9b746b808c17d55dacb44a2efaa 8.1/SRPMS/apcupsd-3.10.5-1.1mdk.src.rpm Mandrake Linux 8.1/IA64: bc0b1ae0605ce9476dfa5777666e3694 ia64/8.1/RPMS/apcupsd-3.8.6-1.1mdk.ia64.rpm a935645bad43e00c7a71445b6781a5b4 ia64/8.1/SRPMS/apcupsd-3.8.6-1.1mdk.src.rpm Mandrake Linux 8.2: d18b5d3fdca353d465e9efc823a10728 8.2/RPMS/apcupsd-3.10.5-1.1mdk.i586.rpm cf73f9b746b808c17d55dacb44a2efaa 8.2/SRPMS/apcupsd-3.10.5-1.1mdk.src.rpm Mandrake Linux 8.2/PPC: 340b9871a68a4d7347633a1c61fa8d1e ppc/8.2/RPMS/apcupsd-3.10.5-1.1mdk.ppc.rpm cf73f9b746b808c17d55dacb44a2efaa ppc/8.2/SRPMS/apcupsd-3.10.5-1.1mdk.src.rpm Mandrake Linux 9.0: 9031edab8f3e692b6c5dbc8717819d8b 9.0/RPMS/apcupsd-3.10.5-1.1mdk.i586.rpm cf73f9b746b808c17d55dacb44a2efaa 9.0/SRPMS/apcupsd-3.10.5-1.1mdk.src.rpm ________________________________________________________________________ Bug IDs fixed (see https://qa.mandrakesoft.com for more information): ________________________________________________________________________ To upgrade automatically, use MandrakeUpdate. The verification of md5 checksums and GPG signatures is performed automatically for you. If you want to upgrade manually, download the updated package from one of our FTP server mirrors and upgrade with "rpm -Fvh *.rpm". A list of FTP mirrors can be obtained from: http://www.mandrakesecure.net/en/ftp.php Please verify the update prior to upgrading to ensure the integrity of the downloaded package. You can do this with the command: rpm --checksig <filename> All packages are signed by MandrakeSoft for security. You can obtain the GPG public key of the Mandrake Linux Security Team from: https://www.mandrakesecure.net/RPM-GPG-KEYS Please be aware that sometimes it takes the mirrors a few hours to update. You can view other update advisories for Mandrake Linux at: http://www.mandrakesecure.net/en/advisories/ MandrakeSoft has several security-related mailing list services that anyone can subscribe to. Information on these lists can be obtained by visiting: http://www.mandrakesecure.net/en/mlist.php If you want to report vulnerabilities, please contact security_linux-mandrake.com Type Bits/KeyID Date User ID pub 1024D/22458A98 2000-07-10 Linux Mandrake Security Team <security linux-mandrake.com> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.7 (GNU/Linux) mQGiBDlp594RBAC2tDozI3ZgQsE7XwxurJCJrX0L5vx7SDByR5GHDdWekGhdiday L4nfUax+SeR9SCoCgTgPW1xB8vtQc8/sinJlMjp9197a2iKM0FOcPlkpa3HcOdt7 WKJqQhlMrHvRcsivzcgqjH44GBBJIT6sygUF8k0lU6YnMHj5MPc/NGWt8wCg9vKo P0l5QVAFSsHtqcU9W8cc7wMEAJzQsAlnvPXDBfBLEH6u7ptWFdp0GvbSuG2wRaPl hynHvRiE01ZvwbJZXsPsKm1z7uVoW+NknKLunWKB5axrNXDHxCYJBzY3jTeFjsqx PFZkIEAQphLTkeXXelAjQ5u9tEshPswEtMvJvUgNiAfbzHfPYmq8D6x5xOw1IySg 2e/LBACxr2UJYCCB2BZ3p508mAB0RpuLGukq+7UWiOizy+kSskIBg2O7sQkVY/Cs iyGEo4XvXqZFMY39RBdfm2GY+WB/5NFiTOYJRKjfprP6K1YbtsmctsX8dG+foKsD LLFs7OuVfaydLQYp1iiN6D+LJDSMPM8/LCWzZsgr9EKJ8NXiyrQ6TGludXggTWFu ZHJha2UgU2VjdXJpdHkgVGVhbSA8c2VjdXJpdHlAbGludXgtbWFuZHJha2UuY29t PohWBBMRAgAWBQI5aefeBAsKBAMDFQMCAxYCAQIXgAAKCRCaqNDQIkWKmK6LAKCy /NInDsaMSI+WHwrquwC5PZrcnQCeI+v3gUDsNfQfiKBvQSANu1hdulqIRgQQEQIA BgUCOtNVGQAKCRBZ5w3um0pAJJWQAKDUoL5He+mKbfrMaTuyU5lmRyJ0fwCgoFAP WdvQlu/kFjphF740XeOwtOqIRgQQEQIABgUCOu8A6QAKCRBynDnb9lq3CnpjAJ4w Pk0SEE9U4r40IxWpwLU+wrWVugCdFfSPllPpZRCiaC7HwbFcfExRmPaIRgQQEQIA BgUCPI+UAwAKCRDniYrgcHcf8xK5AKCm/Mq8qP8GE0o1hEX22QsJMZwH5gCfZ72H 8TacOb3oAmBdprf+K6gkdOiIRgQQEQIABgUCOtOieAAKCRCv2bZyU0yB80MeAJ9K +jXt0cKuaUonRU+CRGetk6t9dgCfTRRL6/puOKdD6md70+K5EBBSvsG0OE1hbmRy YWtlIExpbnV4IFNlY3VyaXR5IFRlYW0gPHNlY3VyaXR5QG1hbmRyYWtlc29mdC5j b20+iFcEExECABcFAjyPnuUFCwcKAwQDFQMCAxYCAQIXgAAKCRCaqNDQIkWKmFi+ AJsHhohgnU3ik4+gy3EdFlB2i/MBoACg6lHn5cnVvTcmgNccWxeNxLLZI5e5AQ0E OWnn7xAEAOQlTVY4TiNo5V/iP0J1xnqjqlqZsU7yEBKo/gZz6/+hx75RURe1ebiJ 9F779FQbpJ9Epz1KLSXvq974rnVb813zuGdmgFyk+ryA/rTR2RQ8h+EoNkwmATzR xBXVJb57fFQjxOu4eNjZAtfII/YXb0uyXXrdr5dlJ/3eXrcO4p0XAAMFBACCxo6Z 269s+A4v8C6Ui12aarOQcCDlV8cVG9LkyatU3FNTlnasqwo6EkaP572448weJWwN 6SCXVl+xOYLiK0hL/6Jb/O9Agw75yUVdk+RMM2I4fNEi+y4hmfMh2siBv8yEkEvZ jTcl3TpkTfzYky85tu433wmKaLFOv0WjBFSikohGBBgRAgAGBQI5aefvAAoJEJqo 0NAiRYqYid0AoJgeWzXrEdIClBOSW5Q6FzqJJyaqAKC0Y9YI3UFlE4zSIGjcFlLJ EJGXlA== =yGlX - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+UrxBmqjQ0CJFipgRAkbqAKDVBujdsmG2ldNRmu5suubAB0Z/qwCg31oG yUS5wWAwhIkl4mIieUR4O7U= =dcA5 -----END PGP SIGNATURE-----
As I was the one to submit a Gentoo patch upstream for apcupsd-3.10.1, I can take care of updating the ebuild and testing it on my several UPSes.
okay, add the fixed ebuilds masked and I'll unmask them when I'm ready.
I have added an ebuild for 3.10.5, which covers that end. I will also be adding a 3.8.6 ebuild to cover the other.
And after looking at 3.8.6, I strongly suggest we simply mark 3.10.5 as stable. The new development branch has patches that would have to be developed again for 3.8.6, and being the one that developed the original patches to fix sandbox violations, I'm not really in the mood to do it for the older version. I have been using 3.10.1 on several of my boxen here with no problems for several months, and I see no strict need for the older version unless someone really wants it bad - in which case they are welcome to develop a patch.
glsa sent
