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
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-9710
Published: 2015-05-27
The Btrfs implementation in the Linux kernel before 3.19 does not ensure that the visible xattr state is consistent with a requested replacement, which allows local users to bypass intended ACL settings and gain privileges via standard filesystem operations (1) during an xattr-replacement time windo...

CVE-2014-9715
Published: 2015-05-27
include/net/netfilter/nf_conntrack_extend.h in the netfilter subsystem in the Linux kernel before 3.14.5 uses an insufficiently large data type for certain extension data, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) via outbound network traffic that trig...

CVE-2015-1157
Published: 2015-05-27
CoreText in Apple iOS 8.x through 8.3 allows remote attackers to cause a denial of service (reboot and messaging disruption) via crafted Unicode text that is not properly handled during display truncation in the Notifications feature, as demonstrated by Arabic characters in (1) an SMS message or (2)...

CVE-2015-2666
Published: 2015-05-27
Stack-based buffer overflow in the get_matching_model_microcode function in arch/x86/kernel/cpu/microcode/intel_early.c in the Linux kernel before 4.0 allows context-dependent attackers to gain privileges by constructing a crafted microcode header and leveraging root privileges for write access to t...

CVE-2015-2830
Published: 2015-05-27
arch/x86/kernel/entry_64.S in the Linux kernel before 3.19.2 does not prevent the TS_COMPAT flag from reaching a user-mode task, which might allow local users to bypass the seccomp or audit protection mechanism via a crafted application that uses the (1) fork or (2) close system call, as demonstrate...

Dark Reading Radio
Archived Dark Reading Radio
After a serious cybersecurity incident, everyone will be looking to you for answers -- but you’ll never have complete information and you’ll never have enough time. So in those heated moments, when a business is on the brink of collapse, how will you and the rest of the board room executives respond?