Apache HTTP Server 2.2.11 Released The Apache Software Foundation and the Apache HTTP Server Project are pleased to announce the release of version 2.2.11 of the Apache HTTP Server ("Apache"). This version of Apache is principally a bug fix release. We consider this release to be the best version of Apache available, and encourage users of all prior versions to upgrade. Apache HTTP Server 2.2.11 is available for download from: http://httpd.apache.org/download.cgi Apache 2.2 offers numerous enhancements, improvements, and performance boosts over the 2.0 codebase. For an overview of new features introduced since 2.0 please see: http://httpd.apache.org/docs/2.2/new_features_2_2.html Please see the CHANGES_2.2 file, linked from the download page, for a full list of changes. A condensed list, CHANGES_2.2.11 provides the complete list of changes since 2.2.10. A summary of security vulnerabilities which were addressed in the previous 2.2.10 and earlier releases is available: http://httpd.apache.org/security/vulnerabilities_22.html Apache HTTP Server 1.3.41 and 2.0.63 legacy releases are also currently available. See the appropriate CHANGES from the url above. See the corresponding CHANGES files linked from the download page. The Apache HTTP Project developers strongly encourage all users to migrate to Apache 2.2, as only limited maintenance is performed on these legacy versions. This release includes the Apache Portable Runtime (APR) version 1.3.3 bundled with the tar and zip distributions. The APR libraries libapr and libaprutil (and on Win32, libapriconv) must all be updated to ensure binary compatibility and address many known platform bugs. This release builds on and extends the Apache 2.0 API. Modules written for Apache 2.0 will need to be recompiled in order to run with Apache 2.2, and require minimal or no source code changes. http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/VERSIONING When upgrading or installing this version of Apache, please bear in mind that if you intend to use Apache with one of the threaded MPMs (other than the Prefork MPM), you must ensure that any modules you will be using (and the libraries they depend on) are thread-safe.
Monthly Archives: December 2008
SA-2008-073 – Drupal core – Multiple vulnerabilities
- Advisory ID: DRUPAL-SA-2008-073
- Project: Drupal core
- Versions: 5.x and 6.x
- Date: 2008-December-10
- Security risk: Moderately Critical
- Exploitable from: Remote
- Vulnerability: Multiple vulnerabilities
Description
Multiple vulnerabilities and weaknesses were discovered in Drupal.
Cross site request forgery
The update system is vulnerable to Cross site request forgeries. Malicious users may cause the superuser (user 1) to execute old updates that may damage the database.
Cross site scripting
When an input format is deleted, not all existing content on a site is updated to reflect this deletion. Such content is then displayed unfiltered. This may lead to cross site scripting attacks when harmful tags are no longer stripped from ‘malicious’ content that was posted earlier.
Versions Affected
- Drupal 5.x before version 5.13
- Drupal 6.x before version 6.7
Solution
Install the latest version:
- If you are running Drupal 5.x then upgrade to Drupal 5.13.
- If you are running Drupal 6.x then upgrade to Drupal 6.7.
Note: the robots.txt and .htaccess files have changed and need to be replaced. The settings.php file has not been changed and can be left as it was if upgrading from the current version of Drupal.
If you are unable to upgrade immediately, you can apply a patch to secure your installation until you are able to do a proper upgrade. The patches fix security vulnerabilities, but do not contain other fixes which were released in these versions.
- To patch Drupal 5.12 use SA-2008-073-5.12.patch.
- To patch Drupal 6.6 use SA-2008-073-6.6.patch.
Reported by
Both issues were reported by David Rothstein (David_Rothstein).
Contact
The security team for Drupal can be reached at security at drupal.org or via the form at http://drupal.org/contact.
CVE-2008-5406
Stack-based buffer overflow in Apple QuickTime Player 7.5.5 and iTunes 8.0.2.20 allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a MOV file with “long arguments,” related to an “off by one overflow.” (CVSS:9.3) (Last Update:2009-01-29)