Attacks/Breaches
7/24/2014
02:17 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Travel Agency Fined £150,000 For Violating Data Protection Act

That'll teach them not to retain credit card data in perpetuity.

The UK Information Commissioner's Office (ICO) has fined the online travel company Think W3 ₤150,000 ($254,610.75) for violating the country's Data Protection Act, as well as the Payment Card Industry Data Security Standard (PCI-DSS). This penalty was issued in response to a December 2012 SQL injection attack that breached a Think W3 website and nabbed credit card numbers and other personally identifiable information on more than 1 million customers.

The site in question was a staff car parking system (for maintaining costs and availability of parking) that was created in 2006 and meant for internal use only. Unfortunately, it was installed on the same server that contained the company's main e-commerce application used to store customer personal data.

The car parking system had not undergone penetration testing or internal vulnerability scans before or after implementation -- the argument being that security testing was unnecessary, because it wasn't an external-facing site, and it required users to log in.

By compromising that site, however, attackers were able to obtain admin access to the common server. They then created a custom query to extract and decrypt cardholder data using the encryption key, which was not stored securely on the web server. After grabbing the credit card data (excluding CVV numbers), the attackers went on to lift the associated names, addresses, email addresses, and phone numbers.

The car parking system had never been updated, and the customer data had never been deleted, so when the attackers penetrated in December 2012, they were able to obtain records dating all the way back to 2006. Altogether they lifted 1,163,996 credit and debit card records, 733,397 of which were expired.

Investigators found none of these records were ever put to use for financial fraud.

Under the Data Protection Act, a "data controller" can be slammed with a monetary penalty if there is a "serious contravention" of the act, if it was "likely to cause substantial damage or substantial distress," and if it was deliberate, or if the data controller knew or should have known such a thing would occur, or if the controller "failed to take reasonable steps to prevent" it.

The highest penalty allowed by the law is ₤500,000.

Some of the factors that contributed to the size of the ₤150,000 penalty included the fact that the company failed to comply with PCI-DSS, test the site's security, patch software, update anti-virus software, and implement suitable intrusion detection systems, file-integrity monitoring software, encryption key management, and internal policies.

Another data controller was just fined for a Data Protection Act violation. Jayesh Shah, a marketing company owner from Pune, India, was fined ₤4,000 for failing to notify the ICO that he was changing his notification. He allegedly sent "millions of unsolicited text messages," but the offense was not for spamming, but rather for selling data on individuals to other parties.

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Thomas Claburn
50%
50%
Thomas Claburn,
User Rank: Ninja
7/24/2014 | 4:05:36 PM
data is a liability as well as an asset
When it comes to data storage, less is more.
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-5084
Published: 2015-08-02
The Siemens SIMATIC WinCC Sm@rtClient and Sm@rtClient Lite applications before 01.00.01.00 for Android do not properly store passwords, which allows physically approximate attackers to obtain sensitive information via unspecified vectors.

CVE-2015-5352
Published: 2015-08-02
The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time ...

CVE-2015-5537
Published: 2015-08-02
The SSL layer of the HTTPS service in Siemens RuggedCom ROS before 4.2.0 and ROX II does not properly implement CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, a different vulnerability than CVE-2014-3566.

CVE-2015-5600
Published: 2015-08-02
The kbdint_next_device function in auth2-chall.c in sshd in OpenSSH through 6.9 does not properly restrict the processing of keyboard-interactive devices within a single connection, which makes it easier for remote attackers to conduct brute-force attacks or cause a denial of service (CPU consumptio...

CVE-2015-1009
Published: 2015-07-31
Schneider Electric InduSoft Web Studio before 7.1.3.5 Patch 5 and Wonderware InTouch Machine Edition through 7.1 SP3 Patch 4 use cleartext for project-window password storage, which allows local users to obtain sensitive information by reading a file.

Dark Reading Radio
Archived Dark Reading Radio
What’s the future of the venerable firewall? We’ve invited two security industry leaders to make their case: Join us and bring your questions and opinions!