Attacks/Breaches

6/28/2018
10:45 AM
50%
50%

Ticketmaster UK Warns Thousands of Data Breach

Customers who bought tickets through the site are advised to check for fraudulent transactions with Uber, Netflix, and Xendpay.

Ticketmaster UK has notified tens of thousands of customers that they might be at risk for identity theft and credit card fraud due to a data breach, potentially affecting anyone who bought concert, theater, or sporting event tickets between February 2018 and June 23, 2018, The Guardian reports.

On June 23, Ticketmaster detected malware on a customer support tool hosted by Inbenta Technologies exporting UK customer data (names, physical and email addresses, phone numbers, payment details, and Ticketmaster logins) to an unknown party. Less than 40,000 of its reported 230 million global customers were compromised in the incident, it says.

However, Ticketmaster could come under fire for not disclosing the breach sooner. Monzo, a digital bank, first spotted customers' cards being misused in April and figured out all those affected had shopped at Ticketmaster. Monzo claims it notified Ticketmaster but couldn't get a response. It told customers who had purchased through the site to replace their cards and watch for fraudulent activity from sites including Uber, Netflix, and Xendpay.

Jeannie Warner, security manager at WhiteHat Security, says businesses can prevent third-party software breaches by working with stakeholders to establish vendor security standards, and then communicating those standards to vendors and regularly monitoring vendors' security.

"Educate them, answer their questions, and get their commitment to meeting the standards," she explains. "Establish a timeline to make them achieve compliance, if they are not already compliant."

Read more details here.

Why Cybercriminals Attack: A DARK READING VIRTUAL EVENT Wednesday, June 27. Industry experts will offer a range of information and insight on who the bad guys are – and why they might be targeting your enterprise. Go here for more information on this free event.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/29/2018 | 3:00:03 PM
Re: Less than 40,000 of its reported 230 million global customers were compromised in the incident
what made this approx 2% acquiring by the unknown malicious actors while the other 98% remained safe? That is a good question, what some percentages to start with. It maybe that there migh not have been enough times to download all the data, so people at the top of record set were the lucky ones. Just a guess.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/29/2018 | 2:57:50 PM
Re: Fraud Activity
The advice to change cards is a good first step That is true, better change it periodically than wait for a breach I would say.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/29/2018 | 2:56:36 PM
Re: Fraud Activity
When a breach is confirmed it should be mandated that the data custodian be responsible for providing fraud insurance/services to the individual. That may help, I prefer not to have the problem in the first place. I am fan of any insurance it comes back and hurt the public.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/29/2018 | 2:54:15 PM
Re: "under fire for not disclosing the breach sooner"
don't see a problem with publically declaring a breach until you are confident you have all of the details in order. Makes sense, unless they have all the information better not to speculate otherwise more harm than help.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/29/2018 | 2:52:58 PM
GDPR
Ticketmaster UK has notified tens of thousands of customers that they might be at risk for identity theft and credit card fraud due to a data breach, I wonder what is going to happen under the guidance of GDPR now, it will most likely fall under that regulation.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/29/2018 | 2:15:52 PM
Less than 40,000 of its reported 230 million global customers were compromised in the incident
1.7% compromise. My question would be is this the full extent of the data lost or will more be disclosed in the future? To that end, what made this approx 2% acquiring by the unknown malicious actors while the other 98% remained safe?
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/29/2018 | 2:12:46 PM
Fraud Activity
When a breach is confirmed it should be mandated that the data custodian be responsible for providing fraud insurance/services to the individual. The advice to change cards is a good first step but it doesn't give me the warm and fuzzies that the rest of the >40K individuals are going to heed these actions early.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/29/2018 | 2:10:38 PM
"under fire for not disclosing the breach sooner"
I think its negligent not to work with the >40K individuals to ensure that their finances aren't at further risk, but I don't see a problem with publically declaring a breach until you are confident you have all of the details in order.
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Major International Airport System Access Sold for $10 on Dark Web
Kelly Sheridan, Staff Editor, Dark Reading,  7/11/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14373
PUBLISHED: 2018-07-17
An issue was discovered in LibTIFF 4.0.9. In TIFFFindField in tif_dirinfo.c, the structure tif is being dereferenced without first checking that the structure is not empty and has the requested fields (tif_foundfield). In the call sequences following from the affected library functions (TIFFVGetFiel...
CVE-2018-14374
PUBLISHED: 2018-07-17
An issue was discovered in LibTIFF 4.0.9. A buffer overflow can occur via an empty fmt argument to unixErrorHandler in tif_unix.c, and it can be exploited (at a minimum) via the following high-level library API functions: TIFFClientOpen, TIFFFdOpen, TIFFRawStripSize, TIFFCheckTile, TIFFComputeStrip,...
CVE-2018-14375
PUBLISHED: 2018-07-17
An issue was discovered in LibTIFF 4.0.9. A buffer overflow vulnerability can occur via an invalid or empty tif argument to TIFFRGBAImageOK in tif_getimage.c, and it can be exploited (at a minimum) via the following high-level library API functions: TIFFReadRGBAImage, TIFFRGBAImageOK, and TIFFRGBAIm...
CVE-2018-14378
PUBLISHED: 2018-07-17
An issue was discovered in LibTIFF 4.0.9. A buffer overflow can occur via an invalid or empty tif argument to TIFFWriteBufferSetup in tif_write.c, and it can be exploited (at a minimum) via the following high-level library API function: TIFFWriteTile.
CVE-2018-14363
PUBLISHED: 2018-07-17
An issue was discovered in NeoMutt before 2018-07-16. newsrc.c does not properly restrict '/' characters that may have unsafe interaction with cache pathnames.