ModSecurity - News and Commercial Rules Update

Over the past few months there has been a lot going on with ModSecurity. There was libModSecurity (aka 3.0) release which was covered in details in a recent blog post by Lead Developer @zimmerle. There was also two recent presentations / demos by the core team at BSides Toronto and BlackHat Arsenal Europe.

Finally, both ModSecurity and the Core Rule Set (CRS) also had some notable achievements such as being nominated to the DINACon Award and winning the German Open Source Business Award (OSBAR) which are results of efforts from CRS project leaders.

It's also worth mention that the new edition of OWASP Top Ten features ModSecurity and the CRS under A10: Insufficient Logging & Monitoring under "How to Prevent":

"... There are commercial and open source application protection frameworks such as OWASP AppSensor, web application firewalls such as ModSecurity with the OWASP ModSecurity Core Rule Set, and log correlation software with custom dashboards and alerting."

These are some of the great achievements from the community that supports and contributes to ModSecurity and CRS in a number of ways. Congratulations to all! :)

Also, and as usual, in the last few weeks the SpiderLabs WAF team have also released new commercial rules for ModSecurity Web Application Firewall (WAF) v2.9 and above. These rules' purpose is to protect against new emerging attacks that target vulnerabilities in public software.

For this release we are highlighting virtual patches for Oracle WebLogic (CVE-2017-10271 / CVE-2017-3506) and JBoss RCE (CVE-2017-12149). These issues could allow an attacker to perform Remote Code Execution attacks.

The Oracle WebLogic issues happens because of unsafe XML deserialization using Java XMLDecoder in the CoordinatorPortType web service. Attackers may send crafted XML documents to the web service which causes WebLogic to deserialize it allowing an attacker to construct arbitrary Java objects and invoke their methods resulting in remote code execution (RCE)

The JBoss issue takes place at the HTTP Invoker service that provides HTTP and RMI access. It's also an unsafe deserialization that happens in the ReadOnlyAccessFilter.java file which receives an object and calls it on the POST data sent by the user without doing validations on the input. This allows sending a maliciously crafted serialized object to the server that when deserialized would trigger the RCE.

These vulnerabilities ranks with a heightened level of risk as there are known exploits in the wild allowing remote and unauthenticated attacks possibly leading to full server compromise by chaining it with other techniques.

ModSecurity Rules from Trustwave® SpiderLabs® include custom virtual patches for public vulnerabilities.

Release Summary

  • Oracle People Soft RCE (CVE-2017-10271) (2180001)
  • Oracle People Soft RCE (CVE-2017-3506) (2180002)
  • Oracle People Soft RCE (2180003)
  • JBoss RCE (body inspection) (CVE-2017-12149) (2180004)
  • JBoss RCE (CVE-2017-12149) (2180005)
  • WordPress Plugin JTRT Responsive Tables 4.1 SQLi (2180006)
  • WordPress Plugin Piwigo 2.9.1 SQLi CVE-2017-10682 (2180007)
  • Joomla! Component NextGen Editor 2.1.0 SQLi (2180008)
  • Joomla! Component JB Visa 1.0 SQLi (2180009)
  • Joomla! Component JBuildozer 1.4.1 SQLi (2180010)
  • Joomla! Component NS Download Shop 2.2.6 SQLi (2170088)
  • Joomla! Component Sponsor Wall 8.0 SQLi (2170089)
  • Joomla! Component Zh YandexMap 6.1.1.0 SQLi (2170090)
  • WordPress Plugin Car Park Booking SQLi (2170091)
  • WordPress Plugin JTRT Responsive Tables 4.1 SQLi (2170092)
  • PHP CityPortal 2.0 SQLi CVE-2017-15970 (2170093)
  • PHP Melody 2.6.1 SQLi CVE-2017-15081 (2170094)
  • MyBuilder Clone 1.0 SQLi CVE-2017-15968 (2170095)
  • Project Management System 1.0 SQLi CVE-2017-15961 (2170096)
  • D-Park Pro 1.0 SQLi CVE-2017-15958 (2170097)
  • Oracle E-Business Suite 12.2.3 - IESFOOTPRINT SQL Injection (2170098)
  • Oracle E-Business Suite 12.x - Server-Side Request Forgery (2170099)
  • Improvements for Struts rules (optional force body inspection rule 21700100)
  • Changes to logging matched parameters

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.