13.07.2015 Views

hp-security-research-cyber-risk-report-pdf-2-w-1408

hp-security-research-cyber-risk-report-pdf-2-w-1408

hp-security-research-cyber-risk-report-pdf-2-w-1408

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

HP Security Research | Cyber Risk Report 2015Vulnerabilities and exploitsIn the past year, significant shifts occurred in how <strong>research</strong>ers go about finding weaknesses inan enterprise’s attack surface. The hunt is on for vulnerabilities in foundational technologies onwhich corporations rely to provide core business functionality. Multiple times in the last year,high-profile vulnerabilities were discovered that left enterprises scrambling to deploy patchesand clean up compromised machines.Even with this shift in focus, our adversaries are still leveraging classic avenues for attack.Exploitation of widely deployed client-side and server-side applications are still commonplace.Browser-based use-after-free (UAF) vulnerabilities are the vector of choice when attackingenterprises and government agencies. Corporations are also unaware of the <strong>risk</strong> imposed onthem by using poorly coded middleware applications. Trends in submissions to the HP Zero DayInitiative highlight the dynamic nature of the attack surfaces to which enterprises are exposedon a daily basis. Having insight into these trends will help users better prepare for the evolvingnature of threats.Exposing weaknesses in OpenSSLWatching the industry respond to the Heartbleed vulnerability highlighted how unprepared wewere for this type of disclosure. The flaw allowed for an unauthenticated remote attacker todisclose the memory of an application that uses the vulnerable version of OpenSSL. Successfulattacks could result in the disclosure of SSL private keys, username/password combinations,and session tokens. Exploitation of this flaw typically would not leave any signs of abnormalbehavior in the application’s logs. It was a silent but serious threat to secure communicationon the Internet.This vulnerability also changed how the industry responded to vulnerability disclosures. Dueto the severity and active exploitation of the vulnerability, corporations were forced to respondquickly, patching servers that were not routinely patched. The issue existed in an applicationlibrary that did not have a clear update path. Enterprises did not have a solid understandingof which applications were using this library and where it was located inside their networks.Large software companies such as Microsoft have patching schedules so IT staff (users) canplan for the rollout of an update. In this case, network administrators were left to hunt allapplications using the vulnerable version of the library and then manually apply the patch.Many organizations could not deploy the patches fast enough and struggled to defend againstincoming attacks.13

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!