Attacks/Breaches
5/8/2009
04:09 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

UC Berkeley Health Service Data Stolen By Overseas Criminals

The breach went undiscovered for six months, during which time Social Security numbers and health insurance information were stolen.

For six months, hackers had access to a server at the University of California, Berkeley, and stole personal information associated with as many as 160,000 students, alumni, and parents.

In an uncommonly thorough disclosure, a UC Berkeley spokeswoman said that the data breach began on Oct. 9, and lasted through April 9, when university IT personnel found messages left by the hackers and took action to close the breach.

The compromised server housed information from the UC Berkeley campus health services center and contained "Social Security numbers, health insurance information, and nontreatment medical information, such as immunization records and names of some of the physicians they may have seen for diagnoses or treatment," according to the spokeswoman.

It did not contain medical records such as patient diagnoses, treatments, or therapies.

On Friday, UC Berkeley began notifying students, alumni, and parents -- who may have personal information on student health service insurance forms -- that their personal information had been accessed without authorization. They also began notifying about 3,400 Mills College students who received health care through UC Berkeley.

The data in question dates back to 1999 for those affiliated with UC Berkeley and to 2001 for those affiliated with Mills College.

Shelton Waggener, UC Berkeley's associate vice chancellor for information technology and its CIO expressed regret for the incident and assured those affected that the university is committed to reducing its exposure to future attacks. He said that the university is working with law enforcement to investigate the incident.

The university has set up a 24-hour data theft hot line, 888-729-3301, to field inquiries and address concerns. Its Web site includes links to credit reporting agencies for requesting fraud alerts and obtaining credit reports, advisable steps to mitigate the risk of identity theft.

A university spokesperson did not immediate respond to a request for information about the method of attack. The incident FAQ document characterizes the attackers as "overseas criminals" and says they "were highly skilled and broke in using a number of different techniques." Further details may not emerge until the university completes its investigation.

Slavik Markovich, CTO of database security company Sentrigo, speculates that the hackers probably got in through a SQL injection attack on a public Web application.

He said it's not clear whether the hackers targeted UC Berkeley specifically or merely spotted a weakness in the university's network. "I think they just did some smart Google searches for certain errors and then started to target the application," he said.

Though he credits the university for having a prepared security response to the incident, he said IT personnel there could have done more to keep an eye on things. "The fact that it took them more than half a year to find out about the breach indicates that they do not have the correct policies and tools to monitor database access and behavior," he said.

He also said that the university should not have had databases containing information with different levels of sensitivity on the same server.


InformationWeek Analytics has published an independent analysis on the current state of security. Download the report here (registration required).

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.