Channel BannerChannel Banner
R7VVwfh0WpoR7VVwfh0Wpo

How This SQL Command Blew Up a Billion Dollar Company

830,330
Socialcounts.Org
Enter Fullscreen (f)
22,957
likes
488
comments
daily view 0
monthly view 0

Share

Live Analytics

Comments 0

How This SQL Command Blew Up a Billion Dollar Company Analytics Table

Income Estimates for How This SQL Command Blew Up a Billion Dollar Company

Based on this YouTube video's total view count of 830K views and industry-standard rates, the estimated total earning is $581 - $1.66K through ad revenue. Historical data is not yet available to calculate daily, weekly, or monthly averages.

About How This SQL Command Blew Up a Billion Dollar Company

Explore How This SQL Command Blew Up a Billion Dollar Company with 830,330 views, 22,957 likes, and 488 comments. Experience the impact of this video content that has captured audience attention.

A story of the Heartland Payment Systems breach from 2007-2009, the world's largest at the time. The specific details of how everything went down is unknown, so this is built on top of the USSS/FBI advisory, and various articles. The FBI advisory (see the third source) covered dozens of breaches that occurred in the late 2000s, all of which had the same attack pattern (Windows, SQL Server, xp_cmdshell, etc). But it's theoretically possible that Heartland was the odd one out, and that everything in this video is wrong ā˜ŗļø SQL injection simulator: https://www.hacksplaining.com/exercises/sql-injection Sources: https://www.bankinfosecurity.com/heartland-breach-inside-look-at-plaintiffs-case-a-1844 https://blog.comodo.com/e-commerce/the-heartland-breach-a-cautionary-tale-for-e-commerce/ https://www.researchgate.net/publication/346975125_Heartland_Data_Breach_Analysis (***Link to FBI advisory is reference [7]***) https://community.fico.com/s/blog-post/a5Q8000000082EYEAY/fico1028 https://www.wired.com/images_blogs/threatlevel/2009/08/gonzalez.pdf https://www.darkreading.com/attacks-breaches/russian-hackers-sentenced-in-heartland-payment-systems-breach-case https://www.forbes.com/sites/davelewis/2015/05/31/heartland-payment-systems-suffers-data-breach/?sh=70856134744a https://www.justice.gov/opa/pr/two-russian-nationals-sentenced-prison-massive-data-breach-conspiracy https://www.cutimes.com/2015/06/05/heartland-suffers-second-breach-attack/ https://kwcsec.gitbook.io/the-red-team-handbook/infrastructure/sql/ms-sql/privilege-escalation https://www.hypr.com/security-encyclopedia/nt-lan-manager https://blog.quest.com/ntlm-authentication-what-it-is-and-why-you-should-avoid-using-it/ https://www.crowdstrike.com/cybersecurity-101/ntlm-windows-new-technology-lan-manager/ Assumptions: - In the hackers' conversation at 1:05, I arbitrarily chose Gonzalez as the "boss" since he's the only one with a Wikipedia page and I suppose has the longest resume. - For 1:38, Amazon does not use a relational database for its product listings, and therefore no SQL queries are used in reality. But this is a relatable and simple example. - At 2:38, whether or not Heartland used the 2000 version of SQL Server is a guess. The above Research Gate paper "Heartland Data Breach Analysis" says 2000 is likely as the website was developed 8 years prior. I believe xp_cmdshell was also first introduced in SQL Server 2000, so it could not have been a version prior to that one. - Whether or not the web portal was connected to SQL Server with sysadmin credentials is also a guess (5:03). It is possible that the role was not sysadmin, but was granted permission to execute xp_cmdshell for unknown reasons (sysadmin can grant other roles permission to use xp_cmdshell) - Heartland's use of NTLM (7:07) is also a guess. Many companies would have not switched over at the time, and the FBI advisory points out the use of fgdump, which is specifically used for NTLM. - It is alluded to at 9:02 and onward, but credentials and privilege escalation could have also been obtained through other means. - The whole "privilege escalation + hop through various hosts" illustration at 9:18 could be completely wrong, and is the biggest gap in the story. This is just the simplest way the payment network could have theoretically been reached. For all we know the hackers actually did exploit Microsoft Office to hack into the mainframe. - Heartland never specifically said what the packets contained (9:34), but they mentioned everything that *wasn't* leaked, like SSNs, so the assumption here is that packets contained everything that they didn't say wasn't leaked. - There's a HSM (hardware security module) section in the FBI advisory as well, but I figured that wasn't too important as the primary issue mentioned throughout every article is the unecrypted in-flight data. Error corrections: - 3:17 dll files literally contain machine code, usually compiled from C or C++ Chapters: 0:00 Brief introduction of Heartland 0:44 The Beginning 1:34 SQL and SQL injection 2:37 Heartland's use of SQL Server 5:41 Almost Caught? 6:13 Jump to the payment network 9:57 Attack shut down, public disclosure 10:48 The Perpetrators 11:24 Preventive measures 12:54 Conclusion Music: Aloft (by LEMMiNO) - https://www.youtube.com/watch?v=XNEKdkB_kdc "Film Noir Background Music for Videos I Noir Jazz Playlist I No Copyright Music" - https://www.youtube.com/watch?v=iYOvAO1rAM0 Twitter: https://twitter.com/kevinfaang/ Instagram: https://instagram.com/kevinfaang_yt/

About YouTube Real-Time View Count

With SocialCounts.org’s view counter, track your YouTube video’s live view count and YouTube likes count in real time with fast, reliable updates.

Watch every YouTube video live view count rise with our real-time YouTube views tracker—built for accuracy and minimal delay.

Follow YouTube real time views as they happen, using our dedicated view counter for YouTube videos.

Get up-to-date live view count on YouTube and see real-time growth with SocialCounts.org’s smart tracking tools.

Embed Widget

Parameters:

  • fullscreen=true - Fullscreen counter
  • graph=true - Live graph chart
  • counter=0/1/2 - Select counter (0=likes, 1=views, 2=comments)
URL

Click to copy the embed URL to your clipboard