Risk
7/7/2009
05:48 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

Social Security Number Prediction Makes Identity Theft Easy

Posting your birthday on Facebook could help identity thieves predict your Social Security number, a new study finds.

Online information about your date of birth and place of birth could allow identity thieves to guess your Social Security number, according to a paper by two Carnegie Mellon researchers.

The paper, published on Monday in The Proceedings of the National Academy of Sciences, details the "unexpected privacy consequences" that arise when disparate data sources can be correlated.

The authors of the study, Alessandro Acquisti, an associate professor of information technology and public policy at CMU's Heinz College, and Ralph Gross, a postdoctoral researcher, demonstrate that Social Security numbers can be predicted using basic demographic data gleaned from government data sources, commercial databases, voter registration lists, or online social networks.

Knowing a person's Social Security number (SSN), name, and date of birth is typically enough to allow an identity thief to impersonate that person for the purpose of various kinds of fraud. Thus, being able to easily guess a person's SSN presents a significant security risk.

Acquisti and Gross estimate that 10 million American residents publish their birthdays in online profiles, or provide enough information for their birthdays to be inferred.

The accuracy with which SSNs can be predicted in 100 attempts varies, based on the availability of online data and on the subject's date and place of birth, from 0.08% to over 10% for some states.

Such odds may not seem particularly dangerous, but an attacker could use a computer program to guess and guess again, over and over. With 1,000 attempts, a SSN becomes as easy to crack as a 3-digit PIN. Among those born recently in small states, the researchers were able to predict SSNs with 60% accuracy after 1,000 attempts.

In their paper, Acquisti and Gross pose a hypothetical scenario in which an attacker rents a 10,000 machine botnet to apply for credit cards in the names of 18-year-old residents of West Virginia using public data. Based on various assumptions, such as the number of incorrect SSN submissions allowed before a credit card issuer blacklists a submitting IP address (3), they estimate that an identity thief could obtain credit card accounts at a rate of up to 47 per minute, or 4,000 before every machine in the botnet got blocked.

Based on an estimated street price that ranges from $1 to $40 per stolen identity, identity thieves in theory could make anywhere from $2,830 to $112,800 per hour.

As a temporary defensive strategy, the authors recommend that the Social Security Administration fully randomize the assignment of new SSNs, instead of randomizing only the first three digits, as the agency recently proposed. But, they note, such measures would not protect existing SSNs.

They also suggest that legislative defenses, such as SSN redaction requirements, won't work either.

"Industry and policy makers may need, instead, to finally reassess our perilous reliance on SSNs for authentication, and on consumers' impossible duty to protect them," the paper concludes.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.