TrustKeeper Scan Engine Update

Summary

A remote code execution vulnerability in Samba was disclosed last week, which affects Samba versions 3.0.x – 3.6.3 and could allow root access to an affected system from an anonymous user. This TrustKeeper Scan Engine update includes vulnerability checks for this issue.

Jonathan Claudius of SpiderLabs discovered the Support Incident Tracker (SiT) vulnerability included in this update. For more details on the SiT vulnerability, visit the Trustwave Security Advisories Page.

This update also includes checks for vulnerabilities in Apache, Bitweaver, Jetty, Movable Type, OpenSSL, OpenSSH, osCommerce, PHP and other products.

New Vulnerability Test Highlights

Some of the more interesting vulnerability tests added recently are as follows:

  • Samba
    • Samba Remote Procedure Call (RPC) Code Generator Remote Code Execution Vulnerability (CVE-2012-1182)
  • Apache
    • Subversion NULL-Pointer Dereference via lock token Vulnerability (CVE-2011-0715)
    • Subversion SVNPathAuthz Disabled Access Control Vulnerability (CVE-2011-1921)
    • HTTP Server PCRE Integer Overflow Vulnerability (CVE-2005-2491)
    • HTTP Server ssl_engine_io.c Denial of Service Vulnerability (CVE-2004-0113)
    • HTTP Server filestat.c Device Name Denial of Service Vulnerability (CVE-2003-0134)
    • HTTP Server mod_ssl Context-Sensitive Cipher Suite Restriction Bypass Vulnerability (CVE-2004-0885)
    • HTTP Server mod_setenvif .htaccess File Privilege Escalation Vulnerability (CVE-2011-3607)
  • Bitweaver
    • Local File Inclusion Vulnerability in style parameter (CVE-2010-5086)
    • CRLF Injection Vulnerability in index.php (CVE-2006-3105)
    • Sensitive Information Disclosure Vulnerability in users/index.php (CVE-2006-3104)
    • Cross-site Scripting Vulnerability in feedback parameter (CVE-2006-3103)
    • SQL Injection Vulnerability in newsletters/edition.php (CVE-2006-6923)
    • Cross-site Scripting Vulnerability in highlight parameter (CVE-2008-4337)
    • Cross-site Scripting Vulnerability in error parameter (CVE-2006-3103, CVE-2006-1745)
    • Sensitive Information Disclosure Vulnerability in sort_mode parameter (CVE-2006-6923)
  • Jetty
    • Directory Listing Request Cross-Site Scripting Vulnerability (CVE-2009-1524)
    • HTTP Server Content-Length Denial of Service (CVE-2004-2381)
  • Movable Type
    • Multiple Cross-site Scripting Vulnerabilities (CVE-2011-5084, CVE-2011-5085)
  • OpenSSL
    • Denial of Service in ECDH CipherSuite (CVE-2011-3210)
  • OpenSSH
    • Resources Exhausion Bug via GSSAPI (CVE-2011-5000)
  • osCommerce
    • Multiple Cross-site Scripting Vulnerabilities (CVE-2012-0312, CVE-2012-0311)
    • Local File Inclusion Vulnerability in readme_file parameter (CVE-2005-2330)
  • PHP
    • Denial of Service in PCNTL Extension (CVE-2011-0753)
    • Denial of Service in grapheme_extract Function (CVE-2011-0420)
    • Denial of Service in zip_fread Function (CVE-2011-1471)
  • Redmine
    • Cross Site Scripting Vulnerability in PATH_INFO (CVE-2011-1723)
  • Support Incident Tracker (SiT)
    • Cross-site Scripting Vulnerability in id parameter (CVE-2012-2235)

General Improvements

The TrustKeeper Scan Engine is one of few vulnerability scanners that attempt to better understand the web application that is installed using a technique called "Web Application Fingerprinting". This allows for more precise attacks to hinge on this context resulting in a more accurate understanding of the application and higher vulnerability detection rates.

Some of the Web Application Fingerprint improvements we have made recently are as follows:

  • Adobe ColdFusion
  • Cisco Unified Communications Manager
  • Jetty HTTP Server
  • Microsoft Terminal Services Web Access
  • Movable Type
  • osCommerce
  • Redmine
  • XAMPP

How to Update?

All Trustwave customers using the TrustKeeper Scan Engine receive the updates "auto-magically" as soon as an update is available. No action is required.

Trustwave reserves the right to review all comments in the discussion below. Please note that for security and other reasons, we may not approve comments containing links.