Author Archive

Alex Horan

Alex Horan is a Senior Product Manager for Core Security Technologies. Previously he ran the System Engineering team at Core Security Technologies, helping to provide training and customer support services to CORE IMPACT'S user base. Alex has over 12 years of experience working with both software and hardware-based security tools. He brings a deep knowledge and understanding of vulnerability assessment and penetration testing, as well as systems and network administration and auditing to his work at Core. Alex has previously worked for mid and large-sized companies helping to design and maintain their security posture.

Tracing Gonzalez’ Footsteps: Exploiting “Low-Risk” SQL Injection

Friday, September 4th, 2009

Here’s what we need to learn from the many crimes of Alex Gonzalez unwrapped in the federal indictments pending against him for allegedly breaking into the networks of several giant corporations and stealing mountains of their most closely-guarded electronic data – sometimes what appears to be your least critical IT vulnerability, from a business perspective, might prove to be the one that gets you.

(And why most organizations, based on that reality, need to find a more efficient manner of understanding the implications of individual vulnerabilities to better assess their overall level of IT risk.)

519-albert_gonzalez_embedded_prod_affiliate_56In the case of the much maligned Heartland Data Systems, this scenario is exactly what appears to be what did them in, at least based on the charges leveled at Gonzalez and some of his unidentified (and yet-to-be incarcerated) “business” partners.

For these companies, which were already spending copious amounts of time and money trying to protect their customers’ credit card information, it looks as if Gonzalez et al were able to identify flaws that did not by themselves expose protected data – and as a result likely received less attention from risk assessors than other vulnerabilities – and then leverage those “low-priority” weak points to tunnel deeper into the businesses’ most sensitive networks and databases.

The real irony is that, since they’d already been certified as compliant with the Payment Card Industry (PCI) Data Security Standard – a set of data security regulations required by the world’s largest credit and debit card providers, these organizations almost certainly had the information that would have helped them figure out just how someone like Gonzalez could do exactly what he did in their hands – they just didn’t have the right filter through which to translate it to show them just what was indeed possible.

These companies had been compelled to conduct fairly thorough vulnerability scanning of their networks and even some penetration testing, as these are processes required under PCI, but couldn’t see through the data to identify the broader risks.

The Problem With Most Risk Assessments

core_icon_redAs I recounted this story during a Webcast that Core Security hosted for roughly 1,000 attendees yesterday, many of the security auditors that I speak to can cite stories similar to the fate that befell the companies compromised by Gonzales; where auditors have identified a vulnerability that allows some level of access to a server or data that is of little value to the organization and the business focuses on the value of the data exposed, but ends up paying for that mistake.

The pain the auditors express to me is in finding a way to convince IT and business management that this issue should not be examined in a vacuum (and as a result be given a low risk rating) but be seen in the context of the network as a whole.

Fortunately for those auditors armed with IMPACT Pro, they can produce an attack graph that diagrams just how a single vulnerability often exposes other parts of the network, and try to use that to convince decision makers what they really need to do to prioritize risks.

And I’d argue that this example provided by Gonzalez is a virtual template for most of the successful data theft incidents that we’re seeing throughout corporate and government IT environments today.

Because of the pervasiveness of security vulnerabilities, particularly in newer technologies such as Web applications, and the intrinsic interconnectivity of IT systems, attackers are able to find small fissures in organizations’ security perimeters and then use those weak points to eventually get their hands on their most valuable electronic assets.

In illustrating the specific SQL injection and escalation techniques employed by Gonzalez in his campaigns utilizing our flagship penetration testing solution, IMPACT Pro, and demonstrating precisely how these actions can be carried out using the product’s patented agent technology – which allows testers to exploit a single vulnerability and then pivot internally using other vulnerabilities resident across Web applications networks, endpoints – I think we also provide the strongest case for the incredible strategic value that our technology provides to its users. 

By going one step further and performing penetration tests against those vulnerabilities discovered during the PCI assessment process using a system like CORE IMPACT that allows you to understand how a low-level SQL injection vulnerability in your Web application can provide attackers with subsequent access to your most closely protected databases, the organizations targeted by Gonzalez could have sorted through their security data and gotten a much clearer view of their most critical risks before these types of electronic data catastrophes ever occurred.

Again, for those of you who didn’t see the Gonzalez webcast, you can find it here.

-Alex Horan, Product Management Director

 

To comment on this blog, please CLICK HERE.

The Thing with Zero Days…

Friday, May 8th, 2009

People frequently ask us at security conferences, or during product demos: “What does CORE IMPACT do to help customers address zero-days?”

Zero days are an interesting topic to consider, one where I believe there is still some misunderstanding of the actual phenomenon, though it’s clearly an area of IT risk that a lot of people are talking about.

I assume that people are concerned with this issue because they’ve been hearing about malware campaigns that target vulnerabilities that no one has reported publicly before the attacks are discovered. That’s the true definition of a “zero-day” flaw – one that was unheard of, and therefore un-patched, before it was found in the wild.

zdt_bookjacket_hirezHowever, some people confuse known vulnerabilities that haven’t been patched, or those that haven’t previously been used in attacks, as falling under the zero-day umbrella. That’s not the case, as anything that’s been reported, whether it’s been fixed or remains unfixed, has already been elevated beyond true zero-day status.

So, to the question, “does CORE IMPACT test for zero days?” The answer is no, but only because we embrace public disclosure, not because we aren’t working to keep our users ahead of new threats. With known issues that remain un-patched, or those that are simply new to the malware community, we’ll always try to have working exploits.

With true zero-day vulnerabilities uncovered by CoreLabs, our first action will always be to contact the involved vendor to tell them everything we know about the problem – and to help in the timely development of a solution for vulnerable users.

The existence of the problem, along with all the details necessary to understand its risk and to obtain and deploy a solution must be disclosed to all affected users, as well as other stakeholders.

And at that point, it’s no longer a zero day.

In the real world vulnerabilities are exploited whether they are publicly disclosed or not, and attackers pick those they use based on their potential value and “return on investment.”

One of the biggest advantages of embracing public disclosure is that by informing everyone about known issues, this effectively turns a zero day into a known commodity and increases its “decay rate,” thereby decreasing its malicious value.

This highlights one of the main reasons that Core is in business today – because we can level the playing field for organizations when it comes to issues like zero day vulnerabilities by arming them with the same information that people are using to create electronic attacks.

Vendors and customers need to be informed of new security vulnerabilities ASAP to educate the vulnerable population about problems and provide them with sufficient information to make informed decisions about managing risk.

In cases when a vendor delays publication of an advisory or patch beyond reasonable expectations, or enough information becomes public for in-the-wild exploitation – including the release of any so-called “silent patches” – we are forced to release our security advisories and exploit code to customers so that they can test workarounds and defenses against any emerging threats.

As vendors prepare their solutions, our developers are already building and testing exploits addressing the involved vulnerabilities so our customers can ensure that they’re protected as soon as problems go public.

So, does Core release zero days? The simple answer is that we do not. The moment our researchers discover a new vulnerability we report it to the vendor and begin leading the process to help everyone become informed of and protected from the issue.

While not everyone in the community shares this approach, to us, it’s just the best way to do business.

-Alex Horan, Senior Product Manager