Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

4/1/2011
06:18 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

RSA SecureID Attack Began With Excel File Rigged With Flash Zero-Day

Phishing email titled '2011 Recruitment Plan' hit RSA user inboxes, stole user credentials -- but no word on exactly what the attackers grabbed

Turns out the targeted attack that exposed RSA's SecurID technology started with one of the oldest tricks in the book: a phishing email with an infected attachment, according to new details revealed today by RSA and security analysts.

This is the first public word from RSA, which has been extremely tight-lipped about details since it went public with an announcement of what it described as an advanced persistent threat (APT)-type attack. RSA today stopped short of telling just what information or technology was taken by the attackers, however.

RSA said two different phishing emails were sent to two small groups of low-level users who received emails with the subject line "2011 Recruitment Plan." The messages came with an Excel attachment that was rigged with the newly patched Adobe Flash zero-day, which was seen in limited targeted attacks earlier this month by Adobe.

"The email was crafted well enough to trick one of the employees to retrieve it from their Junk mail folder, and open the attached excel file," said Uri River, head of new technologies, consumer identity protection at RSA, EMC's security division, in a blog post today.

The attack then installed a Poison Ivy variant for remotely controlling the infected machine "in a reverse-connect mode that makes it more difficult to detect as the PC reaches out to the command and control rather than the other way around," River blogged.

The exploit, a Trojan, stole user credentials from RSA employees, including IT staff, and eventually gained privileged access to the targeted system, according to Avivah Litan, vice president and distinguished analyst with Gartner.

Security researcher Dan Kaminsky says details of the attack without information on what was lost and what it specifically means to SecurID customers is not all that helpful. "The fundamental question of, 'What can an attacker do today that he couldn't do yesterday, for what class attacker, to what class customer' has not been addressed. So as far as I'm concerned, no actionable intelligence has been disclosed," Kaminsky says. "That being said, this nasty habit of blaming the victim from a position of moral superiority has to stop. We're all in trouble, and anyone who thinks they're not potentially compromised today is fooling themselves."

RSA's River said the attacker first harvested access credentials -- user, domain admin, and service accounts. "They performed privilege escalation on non-administrative users in the targeted systems, and then moved on to gain access to key high value targets, which included process experts and IT and Non-IT specific server administrators," he blogged.

"The attacker in the RSA case established access to staging servers at key aggregation points; this was done to get ready for extraction. Then they went into the servers of interest, removed data and moved it to internal staging servers where the data was aggregated, compressed and encrypted for extraction," he said.

Password-protected RAR files were transferred via FTP from the RSA file server to an external machine that had been compromised at a hosting service provider. "The files were subsequently pulled by the attacker and removed from the external compromised host to remove any traces of the attack," he said.

Gartner's Litan says RSA said it relied on its NetWitness tools to detect the attack in real time. But the company didn't react to the attack in real time, she says. "They didn’t rely as they should have -- also on user profiling, account profiling used in conjunction with fraud detection rules, and models that run in-line with the transaction stream, which could then trigger a real-time intervention back to the user to verify the user’s legitimacy," Litan says.

RSA could have implemented a rule that would signal an alert if "User X pulls more than five records in 15 minutes," for example, Litan says. "[The alert] then automatically goes back to User X out-of-band with SMS or an automated call, [for example], and asks User X to verify the transaction ... These are the kinds of systems RSA sells to the banks."

While RSA gets kudos for alerting customers quickly about the attack, Litan says RSA should have known better and doesn't appear to be using its own fraud detection technology. "They relied on yesterday's best of breed tools to prevent and detect the attack. They gave a lot of credit to NetWitness for helping them find the attack in real time but they obviously weren't able to stop the attack in real time, which means the signals and scores weren’t high enough to cause a person to shut down the attack immediately," she wrote in her blog on the analyst call.

"RSA sells its own fraud detection systems based on user and account profiling which use statistical Beysian models to spot abnormal behavior and intervene in real time to re-authenticate users and verify the authenticity of suspect access, behavior, or transactions. They should have applied these techniques to their own internal systems. They need to stay innovative and apply the lessons learned from serving their clients to their own internal enterprise systems. They have not done that," Litan wrote.

Meanwhile, the only hint River provided about how RSA is shoring up his defenses was that the company is "making both small-term hardening moves and giant strides toward establishing a whole new defense doctrine. We’re implementing techniques that just a couple of weeks ago I thought were in the realm of long-term road maps."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-25137
PUBLISHED: 2020-09-25
An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to Cross-Site Scripting (XSS) due to the fact that it is possible to inject and store malicious JavaScript code within it. This can occur via the alert_name or alert_message parameter to the /a...
CVE-2020-25138
PUBLISHED: 2020-09-25
An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to Cross-Site Scripting (XSS) due to the fact that it is possible to inject and store malicious JavaScript code within it. This can occur via /alert_check/action=delete_alert_checker/alert_test...
CVE-2020-25139
PUBLISHED: 2020-09-25
An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to Cross-Site Scripting (XSS) due to the fact that it is possible to inject and store malicious JavaScript code within it. This can occur via la_id to the /syslog_rules URI for delete_syslog_ru...
CVE-2020-25140
PUBLISHED: 2020-09-25
An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to Cross-Site Scripting (XSS) due to the fact that it is possible to inject and store malicious JavaScript code within it. This can occur in pages/contacts.inc.php.
CVE-2020-4531
PUBLISHED: 2020-09-25
IBM Business Automation Workflow 18.0, 19.0, and 20.0 and IBM Business Process Manager 8.0, 8.5, and 8.6 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the sy...