Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

Texas Data Breach Exposed 3.5 Million Records

Names, addresses, and social security numbers of state retirees and unemployment beneficiaries were posted, unencrypted, on a public server.

10 Massive Security Breaches
(click image for larger view)
Slideshow: 10 Massive Security Breaches
The Texas comptroller's office began notifying millions of people Monday that their personal data had been involved in a data breach. The private data was posted to a public server, where it was available--in some cases--for over a year.

"I deeply regret the exposure of the personal information that occurred and am angry that it happened," Texas comptroller Susan Combs said in a statement. "I want to reassure people that the information was sealed off from any public access immediately after the mistake was discovered and was then moved to a secure location. We take information security very seriously and this type of exposure will not happen again."

The state's attorney general and the FBI have launched a criminal investigation into the data breach. A state spokesperson told The Dallas Morning News that an unspecified number of people were fired after the breach was discovered on March 31, 2011.

The 3.5 million breached records include 1.2 million records, posted in January 2010, of education employees and retirees from the Teacher Retirement System of Texas. In addition, 2 million records from the Texas Workforce Commission (TWC), which provides unemployment benefits to Texas residents, were posted in April 2010. Finally, 281,000 records from the Employees Retirement System of Texas, involving state employees and retirees, were posted in May 2010.

According to the comptroller's office, "the information was required to be transferred per statute by these agencies and used internally at the comptroller's office as part of the unclaimed property verification system." It also said that "we have no information at this time that the personal information has been misused in any way."

The posted records included people's names, mailing addresses, social security numbers, and in some cases also dates of birth and driver's license numbers. According to the comptroller's office, none of the data was encrypted, even though Texas administrative rules require agencies to encrypt all data files containing sensitive information. Furthermore, established security policies governing how information gets released were not followed.

The leak of social security numbers is dangerous, as they can be used by identity thieves to open bank accounts, secure lines of credit, and apply for credit cards. Accordingly, most organizations that experience a serious data breach, such as this one, extend free credit monitoring services to affected people to help offset the substantial time typically required to clean up any resulting identity theft. To date, Texas has not said it will offer such services to people affected by the comptroller's breach.

Instead, the state has set up an informational website, dubbed Texas Safeguard. Starting Tuesday, the state also began offering a toll-free number that people can call for more information, or to find out if they will be receiving a data breach notification letter. As of Tuesday, however, a message on the Web page noted that while the call center was equipped to receive 19,000 calls per day, and would be staffed 24 hours per day for the first week, it was "currently receiving high call volumes" and might be unavailable.

Perhaps that's not surprising, since based on the volume of potentially compromised records, the call center can only handle inquiries--on a per-day basis--from 0.5% of the people whose personal details were potentially breached.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...