Vulnerabilities / Threats
10/13/2013
10:57 AM
Tim Wilson
Tim Wilson
Quick Hits
50%
50%

Flaw In Chrome May Leave Users' Personal Information At Risk

Vulnerability in Chrome browser could enable attackers to collect data from history files, Identity Finder says

Security flaws in Google Chrome could enable attackers to capture personal data stored in the browser's history files, researchers said Friday.

In a blog posted last week, researchers at security firm Identity Finder outlined methods for accessing personal data from Chrome's History Provider Cache, even if the data has been entered on a secure website. Some data also may be accessible through Chrome's Web Data and History databases, the researchers say.

The researchers found flaws in Chrome's SQLite and protocol buffers, which sometimes store personal information such as names, email addresses, mailing addresses, phone numbers, bank account numbers, Social Security numbers, and credit card numbers.

"Chrome browser data is unprotected, and can be read by anyone with physical access to the hard drive, access to the file system, or simple malware," the blog states. "There are dozens of well-known exploits to access payload data and locally stored files."

The vulnerabilities in Chrome have been known for some time, but the researchers say that their proofs of concept are the first to demonstrate the ease with which attackers could access and steal personal information.

"By connecting the dots, we hope to educate all Chrome users that Chrome stores sensitive data unencrypted, alert users of the risks of stored Chrome data, and encourage individuals and enterprises to engage in sensitive data management best practices," the blog says.

Identity Finder has notified Google of its new research, but has not yet received a response, according to the blog.

Users can protect their personal data by taking simple steps to protect data in the history cache files, Identity Finder says.

"Anytime you enter a credit card number or other [personally identifiable information] into a form, be sure to "Clear saved Autofill form data," "Empty the cache," and "Clear browsing history" from the past hour, and the information you typed will be erased," the blog says. "Alternatively, disabling Autofill or using Incognito mode will protect form data."

Have a comment on this story? Please click "Add a Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-8148
Published: 2015-01-26
The default D-Bus access control rule in Midgard2 10.05.7.1 allows local users to send arbitrary method calls or signals to any process on the system bus and possibly execute arbitrary code with root privileges.

CVE-2014-8157
Published: 2015-01-26
Off-by-one error in the jpc_dec_process_sot function in JasPer 1.900.1 and earlier allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted JPEG 2000 image, which triggers a heap-based buffer overflow.

CVE-2014-8158
Published: 2015-01-26
Multiple stack-based buffer overflows in jpc_qmfb.c in JasPer 1.900.1 and earlier allow remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted JPEG 2000 image.

CVE-2014-9571
Published: 2015-01-26
Cross-site scripting (XSS) vulnerability in admin/install.php in MantisBT before 1.2.19 and 1.3.x before 1.3.0-beta.2 allows remote attackers to inject arbitrary web script or HTML via the (1) admin_username or (2) admin_password parameter.

CVE-2014-9572
Published: 2015-01-26
MantisBT before 1.2.19 and 1.3.x before 1.3.0-beta.2 does not properly restrict access to /*/install.php, which allows remote attackers to obtain database credentials via the install parameter with the value 4.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
If you’re a security professional, you’ve probably been asked many questions about the December attack on Sony. On Jan. 21 at 1pm eastern, you can join a special, one-hour Dark Reading Radio discussion devoted to the Sony hack and the issues that may arise from it.