Drupal megaflaw raises questions over CMS bods' crisis mgmt

Fallout spreads as securobods issue warnings


The security world has been shocked to its foundations following ominous warnings that millions of Drupal websites that didn't apply a critical patch within hours of its release earlier this month should be regarded as hopelessly compromised.

The maintainers of the Drupal content management system warned users that “automated attacks” targeting Drupal version 7 began just hours after they disclosed a highly critical SQL injection vulnerability on 15 October.

“Proceed under the assumption that every Drupal 7 website was compromised unless updated or patched before Oct 15th, 11pm UTC," Drupal said in an "Highly Critical - Public Service announcement" on Wednesday.

The vulnerability in Drupal 7.x could be exploited to gain elevated privileges or execute PHP code through SQL injection attacks. Earlier versions of Drupal were NOT affected by the flaw, which ironically stems from code designed to guard against SQLi attacks.

The CVE-2014-3704 flaw creates a means for hackers to steal information, or much worse, plant malicious code or backdoors on servers running the vulnerable enterprise app. Upgrading to Drupal 7.32 fixes the vulnerability, without removing any backdoors installed by hackers if they managed to compromise a site before it was patched.

In some cases it seems that hackers actually patched vulnerable systems themselves – not as an act of charity but to prevent rival hacking groups getting in.

Finding out if there's a backdoor on a website is a difficult and uncertain business. So rather than simply patching, more drastic action is needed. Drupal’s advice is if there's any doubt then sites need to be rebuilt using backups that pre-date 15 October – or they need to be rebuilt from scratch.

"In a nutshell, if your site wasn’t protected within a few hours of Drupal’s announcement on 15 October, you need to restore it from an old backup or rebuild it from the ground up," said veteran security expert Graham Cluley, in a blog post. "Drupal’s advice will be a hard pill for some sites to follow, but should mean that you can feel confident that your site is not affected.

Panic stations

Gavin Millard, EMEA Technical Director at Tenable Network Security, developers of the Nessus vulnerability scanner, questioned Drupal's handling of the disclosure.

"The issues highlighted by the Drupal team could have been reduced if responsible disclosure followed," Millard said. "Announcing a fundamental flaw in the code to everyone without giving much runway to the users of Drupal to proactively patch, gives ample time for attackers to weaponise the flaw and exfiltrate data or manipulate the systems for later exploitation.”

Stefan Esser of German security outfit SektionEins, the first to post about the vulnerability, added: "We warned Drupal to disclose in a diff [sic] way".

Easy pickings

Ilia Kolochenko, chief exec of web security testing firm High-Tech Bridge, said the circumstances of the flaw made Drupal sites easy picking for even relatively unskilled miscreants.

“As soon as a vulnerability in popular CMS platforms like Drupal is discovered, millions of crawlers operated by hackers (similar to Google bots) start searching for vulnerable websites," Kolochenko explained. "Once a victim is identified, their website gets hacked, patched (to prevent ‘competition’ taking over the same site) and backdoored.”

“Within several days, access to the compromised website will be sold on the black market, more than likely to several different customers at the same time who each may well resell it several more times. Like this, your personal blog may be easily involved in a dozen different criminal offences such as hosting illicit content, sending spam and infecting visitors,” Kolochenko concluded.

Tenable's Millard agreed that the bug was easily exploitable.

“The so-called 'Drupageddon' vulnerability could have easily led to exploitation of any systems running the vulnerable code," Millard said. "With such an easy to exploit flaw, the chance of exfiltration of data or further exploitation are high."

Reviewing log files for signs of attacks would be prudent in the circumstances, Millard concluded.

"For those who have good security controls, reviewing of logs and traffic directed at the sites following the vulnerability being announced and the patch applied is common sense and highly advisable, with appropriate action taken if indicators of compromise are found.”

“For those who don’t have such a good level of security or visibility into the logs, the advice from the Drupal team should be heeded. If you don’t know if you were exploited you should assume that you have been." ®

Similar topics

Broader topics


Other stories you might like

  • AMD claims its GPUs beat Nvidia on performance per dollar
    * Terms, conditions, hardware specs and software may vary – a lot

    As a slowdown in PC sales brings down prices for graphics cards, AMD is hoping to win over the market's remaining buyers with a bold, new claim that its latest Radeon cards provide better performance for the dollar than Nvidia's most recent GeForce cards.

    In an image tweeted Monday by AMD's top gaming executive, the chip designer claims its lineup of Radeon RX 6000 cards provide better performance per dollar than competing ones from Nvidia, with all but two of the ten cards listed offering advantages in the double-digit percentages. AMD also claims to provide better performance for the power required by each card in all but two of the cards.

    Continue reading
  • Google opens the pod doors on Bay View campus
    A futuristic design won't make people want to come back – just ask Apple

    After nearly a decade of planning and five years of construction, Google is cutting the ribbon on its Bay View campus, the first that Google itself designed.

    The Bay View campus in Mountain View – slated to open this week – consists of two office buildings (one of which, Charleston East, is still under construction), 20 acres of open space, a 1,000-person event center and 240 short-term accommodations for Google employees. The search giant said the buildings at Bay View total 1.1 million square feet. For reference, that's less than half the size of Apple's spaceship. 

    The roofs on the two main buildings, which look like pavilions roofed in sails, were designed that way for a purpose: They're a network of 90,000 scale-like solar panels nicknamed "dragonscales" for their layout and shimmer. By scaling the tiles, Google said the design minimises damage from wind, rain and snow, and the sloped pavilion-like roof improves solar capture by adding additional curves in the roof. 

    Continue reading
  • Pentester pops open Tesla Model 3 using low-cost Bluetooth module
    Anything that uses proximity-based BLE is vulnerable, claim researchers

    Tesla Model 3 and Y owners, beware: the passive entry feature on your vehicle could potentially be hoodwinked by a relay attack, leading to the theft of the flash motor.

    Discovered and demonstrated by researchers at NCC Group, the technique involves relaying the Bluetooth Low Energy (BLE) signals from a smartphone that has been paired with a Tesla back to the vehicle. Far from simply unlocking the door, this hack lets a miscreant start the car and drive away, too.

    Essentially, what happens is this: the paired smartphone should be physically close by the Tesla to unlock it. NCC's technique involves one gadget near the paired phone, and another gadget near the car. The phone-side gadget relays signals from the phone to the car-side gadget, which forwards them to the vehicle to unlock and start it. This shouldn't normally happen because the phone and car are so far apart. The car has a defense mechanism – based on measuring transmission latency to detect that a paired device is too far away – that ideally prevents relayed signals from working, though this can be defeated by simply cutting the latency of the relay process.

    Continue reading

Biting the hand that feeds IT © 1998–2022