![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Security Advisories (RSS) UNIX and Linux Security Advisories Via RSS News |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Sendmail, Cyrus, Dovecot | Action | UNIX for Dummies Questions & Answers | 0 | 06-10-2009 12:07 PM |
| Slackware: cyrus-sasl | iBot | Security Advisories (RSS) | 0 | 05-15-2009 12:45 AM |
| GNU SASL 0.2.25 (Default branch) | iBot | Software Releases - RSS News | 0 | 03-21-2008 08:40 PM |
| S-164: Tk Vulnerability | iBot | Security Advisories (RSS) | 0 | 02-11-2008 05:10 PM |
| Cyrus Imap receiving via pop3? | raymax83 | UNIX for Advanced & Expert Users | 2 | 09-07-2003 11:00 AM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|||||
|
USN-790-1: Cyrus SASL vulnerability
Referenced CVEs:
CVE-2009-0688 Description: =========================================================== Ubuntu Security Notice USN-790-1 June 24, 2009 cyrus-sasl2 vulnerability CVE-2009-0688 =========================================================== A security issue affects the following Ubuntu releases: Ubuntu 6.06 LTS Ubuntu 8.04 LTS Ubuntu 8.10 Ubuntu 9.04 This advisory also applies to the corresponding versions of Kubuntu, Edubuntu, and Xubuntu. The problem can be corrected by upgrading your system to the following package versions: Ubuntu 6.06 LTS: libsasl2 2.1.19.dfsg1-0.1ubuntu3.1 Ubuntu 8.04 LTS: libsasl2-2 2.1.22.dfsg1-18ubuntu2.1 Ubuntu 8.10: libsasl2-2 2.1.22.dfsg1-21ubuntu2.1 Ubuntu 9.04: libsasl2-2 2.1.22.dfsg1-23ubuntu3.1 After a standard system upgrade you need to restart services using SASL to effect the necessary changes. Details follow: James Ralston discovered that the Cyrus SASL base64 encoding function could be used unsafely. If a remote attacker sent a specially crafted request to a service that used SASL, it could lead to a loss of privacy, or crash the application, resulting in a denial of service. More... |
| Sponsored Links | ||
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|