The Apache Software Foundation and the Apache HTTP Server Project are
pleased to announce the release of version 2.2.17 of the Apache HTTP
Server ("Apache"). This version of Apache is principally a bug fix
release, and a security fix release of the APR-util 1.3.10 dependency;
* SECURITY: CVE-2010-1623 (cve.mitre.org)
Fix a denial of service attack against apr_brigade_split_line().
* SECURITY: CVE-2009-3560, CVE-2009-3720 (cve.mitre.org)
Fix two buffer over-read flaws in the bundled copy of expat which
could cause httpd to crash while parsing specially-crafted
XML documents.
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.17 is available for download from:
http://httpd.apache.org/download.cgi
Apache HTTP Server 2.0.64 legacy release is also currently available,
with the same vulnerability correction as well as many others fixed in
2.2.16 and earlier releases. 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 and less
frequent maintenance is provided for legacy versions.
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.17 provides the
complete list of changes since 2.2.16. A summary of all of the security
vulnerabilities addressed in this and earlier releases is available:
http://httpd.apache.org/security/vulnerabilities_22.html
This release includes the Apache Portable Runtime (APR) version 1.4.2
and APR Utility Library (APR-util) version 1.3.10, bundled with the tar
and zip distributions. The APR libraries libapr and libaprutil (and
on Win32, libapriconv version 1.2.1) must all be updated to ensure
binary compatibility and address many known security and 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.
CVE-2010-3493
Multiple race conditions in smtpd.py in the smtpd module in Python 2.6, 2.7, 3.1, and 3.2 alpha allow remote attackers to cause a denial of service (daemon outage) by establishing and then immediately closing a TCP connection, leading to the accept function having an unexpected return value of None, an unexpected value of None for the address, or an ECONNABORTED, EAGAIN, or EWOULDBLOCK error, or the getpeername function having an ENOTCONN error, a related issue to CVE-2010-3492. (CVSS:4.3) (Last Update:2013-05-14)
CVE-2010-3492
The asyncore module in Python before 3.2 does not properly handle unsuccessful calls to the accept function, and does not have accompanying documentation describing how daemon applications should handle unsuccessful calls to the accept function, which makes it easier for remote attackers to conduct denial of service attacks that terminate these applications via network connections. (CVSS:5.0) (Last Update:2011-07-18)
Oracle Critical Patch Update (CPU) – October 2010
Security Response – Check your computer for malware
Symantec Security Response has created a short video to introduce you to some of the common hiding places for malware. The video presented by Benjamin Nahorney (Senior Information Developer) takes you through the following topics:
1) Looking for suspicious programs in Windows Startup by using msconfig.
2) Checking the list of running processes and services using Windows Task Manager and services.msc tool.
3) Visually checking the System folders for suspect files with Windows Explorer.
4) Submitting the any suspicious files to Symantec security response for analysis using the Web Sample Submission page.
5) Tracking and reviewing the response provided by Symantec to your submission.
To watch the video click on the following link/image:
http://www.youtube.com/watch?v=gymh_TF818I&fmt=6
For more details and a more comprehensive list of common load points for malware, please see to the following articles:
http://www.symantec.com/business/support/index?page=content&id=TECH99331&locale=en_US
We hope that this video helps you to troubleshoot and identify potentially malicious files that may be causing problems on your computer.
Symantec Security Response Team
08-12-2008 12:12 PM
CVE-2010-3082
Cross-site scripting (XSS) vulnerability in Django 1.2.x before 1.2.2 allows remote attackers to inject arbitrary web script or HTML via a csrfmiddlewaretoken (aka csrf_token) cookie. (CVSS:4.3) (Last Update:2010-11-05)
CVE-2010-1818 (quicktime)
The IPersistPropertyBag2::Read function in QTPlugin.ocx in Apple QuickTime 6.x, 7.x before 7.6.8, and other versions allows remote attackers to execute arbitrary code via the _Marshaled_pUnk attribute, which triggers unmarshaling of an untrusted pointer.
[ANNOUNCEMENT] Apache HTTP Server 2.3.8-alpha Released
Apache HTTP Server 2.3.8-alpha Released
The Apache Software Foundation and the Apache HTTP Server Project are
pleased to announce the release of version 2.3.8-alpha of the Apache HTTP
Server ("Apache"). This version of Apache is principally an alpha release
to test new technology and features that are incompatible or too large for
the stable 2.2.x branch. This alpha release should not be presumed to
be compatible with binaries built against any prior or future version.
This release is expected to be the last alpha release; subsequent releases
will be beta releases as we move towards 2.4.0-GA.
Apache HTTP Server 2.3.8-alpha is available for download from:
http://httpd.apache.org/download.cgi
Apache 2.3 offers numerous enhancements, improvements, and performance
boosts over the 2.2 codebase. For an overview of new features
introduced since 2.3 please see:
http://httpd.apache.org/docs/trunk/new_features_2_4.html
Please see the CHANGES_2.3 file, linked from the download page, for a
full list of changes.
This release includes the Apache Portable Runtime (APR) version 1.4.2
and APR-Util version 1.3.9 in a separate -deps tarball. The APR libraries
must be upgraded for all features of httpd to operate correctly.
This release builds on and extends the Apache 2.2 API. Modules written
for Apache 2.2 will need to be recompiled in order to run with Apache
2.3, and require minimal or no source code changes.
http://svn.apache.org/repos/asf/httpd/httpd/trunk/VERSIONING
CVE-2010-1797
Multiple stack-based buffer overflows in the cff_decoder_parse_charstrings function in the CFF Type2 CharStrings interpreter in cff/cffgload.c in FreeType before 2.4.2, as used in Apple iOS before 4.0.2 on the iPhone and iPod touch and before 3.2.2 on the iPad, allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via crafted CFF opcodes in embedded fonts in a PDF document, as demonstrated by JailbreakMe. NOTE: some of these details are obtained from third party information. (CVSS:9.3) (Last Update:2012-12-18)
SA-CORE-2010-002 – Drupal core – Multiple vulnerabilities
- Advisory ID: DRUPAL-SA-CORE-2010-002
- Project: Drupal core
- Version: 5.x, 6.x
- Date: 2010-August-11
- Security risk: Critical
- Exploitable from: Remote
- Vulnerability: Multiple vulnerabilities
Description
Multiple vulnerabilities and weaknesses were discovered in Drupal.
OpenID authentication bypass
The OpenID module provides users the ability to login to sites using an OpenID account.
The OpenID module doesn’t implement all the required verifications from the OpenID 2.0 protocol and is vulnerable to a number of attacks.
Specifically:
– OpenID should verify that a “openid.response_nonce” has not already been used for an assertion by the OpenID provider
– OpenID should verify the value of openid.return_to as obtained from the OpenID provider
– OpenID must verify that all fields that are required to be signed are signed
These specification violations allow malicious sites to harvest positive assertions from OpenID providers and use them on sites using the OpenID module to obtain access to preexisting accounts bound to the harvested OpenIDs. Intercepted assertions from OpenID providers can also be replayed and used to obtain access to user accounts bound to the intercepted OpenIDs.
This issue affects Drupal 6.x only. A separate security announcement and release is published for the contributed OpenID module for Drupal 5.x.
File download access bypass
The upload module allows users to upload files and provides access checking for file downloads.
The module looks up files for download in the database and serves them for download after access checking. However, it does not account for the fact that certain database configurations will not consider case differences in file names. If a malicious user uploads a file which only differs in letter case, access will be granted for the earlier upload regardless of actual file access to that.
This issue affects Drupal 5.x and 6.x.
Comment unpublishing bypass
The comment module allows users to leave comments on content on the site.
The module supports unpublishing comments by privileged users. Users with the “post comments without approval” permission however could craft a URL which allows them to republish previously unpublished comments.
This issue affects Drupal 5.x and 6.x.
Actions cross site scripting
The actions feature combined with Drupal’s trigger module allows users to configure certain actions to happen when users register, content is submitted, and so on; through a web based interface.
Users with “administer actions permission” can enter action descriptions and messages which are not properly filtered on output. Users with content and taxonomy tag submission permissions can create nodes and taxonomy terms which are not properly sanitized for inclusion in action messages and inject arbitrary HTML and script code into Drupal pages. Such a cross-site scripting attack may lead to the malicious user gaining administrative access. Wikipedia has more information about cross-site scripting (XSS).
This issue affects Drupal 6.x only.
Versions affected
- Drupal 6.x before version 6.18 or 6.19.
- Drupal 5.x before version 5.23.
Solution
Install the latest version:
- If you are running Drupal 6.x then upgrade to Drupal 6.18 or Drupal 6.19.
- If you are running Drupal 5.x then upgrade to Drupal 5.23.
Drupal 5 will no longer be maintained when Drupal 7 is released. Upgrading to Drupal 6 is recommended.
The security team starts a new practice of releasing both a pure security update without other bugfixes and a security update combined with other bug fixes and improvements. You can choose to either only include the security update for an immediate fix (which might require less quality assurance and testing) or more fixes and improvements alongside the security fixes by choosing between Drupal 6.18 and Drupal 6.19. Read the announcement for more information.
Reported by
The OpenID authentication bypass issues were reported by Johnny Bufu, Christian Schmidt and Heine Deelstra (*).
The file download access bypass was reported by Wolfgang Ziegler.
The comment unpublish bypass issue was reported by Heine Deelstra (*).
The actions module cross site scripting was reported by Justin Klein Keane and Heine Deelstra (*).
(*) Member of the Drupal security team.
Fixed by
The OpenID authentication issues were fixed by Christian Schmidt, Heine Deelstra (*) and Damien Tournoud (*).
The file download access bypass was fixed by Dave Reid (*) and Neil Drumm (*).
The comment unpublish bypass issue was fixed by Heine Deelstra (*).
The actions module cross site scripting was fixed by Justin Klein Keane and Heine Deelstra (*).
(*) Member of the Drupal security team.
Contact
The security team for Drupal can be reached at security at drupal.org or via the form at http://drupal.org/contact.
Drupal version: