Attacks/Breaches
10/22/2012
04:52 PM
Connect Directly
RSS
E-Mail
50%
50%

Who Is Hacking U.S. Banks? 8 Facts

Hackers have labeled the bank website disruptions as grassroots-level reprisal for an anti-Islamic film. But is the Iranian government really backing the attacks?
Previous
7 of 8
Next


Each of the recent DDoS attacks against U.S. financial institutions have this in common: The Izz ad-din Al qassam cyber fighters have claimed credit, and the same PHP-based toolkit, "itsoknoproblembro," has been used to launch at least some of the DDoS attacks involved.

First, the attackers must install the toolkit on targeted servers. "The malicious actors make use of Web application vulnerabilities on thousands of different Web servers in order to drop various flavors of the itsoknoproblembro PHP scripts into available directories," according to the Prolexic report. "Once the files are written to the server, attackers are able to access them to perform unauthorized system functions, check on the bot's status, or launch DDoS attacks."

DDoS attacks today focus both on infrastructure (layers 3 and 4) as well as applications (layer 7), according to Prolexic.

Unlike botnets, Prolexic said that itsoknoproblembro infections aren't managed using a command-and-control (C&C) server, in which infected endpoints retrieve commands from a botmaster. Instead, the itsoknoproblembro infections are controlled by pushing commands to them.

The versatile toolkit can be used to infect a number of different systems. "Itsoknoproblembro scripts have been discovered on servers hosting a variety of platforms, including Awstats, WordPress, Joomla, Plesk, and many others. For example, one of the more popular recent infection vectors is the exploitation of vulnerability within the Joomla Bluestork theme," according to the report.

Unfortunately for U.S. banks, or anyone else targeted via itsoknoproblembro, the vulnerabilities exploited by the toolkit remain hard to fix. "Cleanup efforts for itsoknoproblembro have been extremely difficult and taxing on security experts," according to Prolexic. "Coupled with outdated Web applications and inexperienced administrators, it will be extremely difficult to effectively remediate this infection." While further efforts are underway to find new ways to spot and block related attacks, so far there's been no quick-fix defensive measure discovered.

RECOMMENDED READING

Iran Denies Hacking American Banks, Censors Google

PNC Bank Hit By Crowdsourced Hacktivist Attacks

Bank Site Attacks Trigger Ongoing Outages, Customer Anger

Bank Hacks: 7 Misunderstood Facts

Hackers Launch New Wave Of U.S. Bank Attacks

U.S. Bank Hacks Expand; Regions Financial Hit

Bank Hacks: Iran Blame Game Intensifies

DOD: Hackers Breached U.S. Critical Infrastructure Control Systems

Previous
7 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Leo Regulus
50%
50%
Leo Regulus,
User Rank: Apprentice
10/24/2012 | 4:52:32 PM
re: Who Is Hacking U.S. Banks? 8 Facts
Very disappointed in Editor's choice of article format. This has been extensively discussed in the past.
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.