Risk
7/7/2009
05:48 PM
Connect Directly
Google+
LinkedIn
Twitter
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
Comments
Threaded  |  Newest First  |  Oldest First
Printers: The Weak Link in Enterprise Security
Kelly Sheridan, Associate Editor, Dark Reading,  10/16/2017
20 Questions to Ask Yourself before Giving a Security Conference Talk
Joshua Goldfarb, Co-founder & Chief Product Officer, IDDRA,  10/16/2017
Why Security Leaders Can't Afford to Be Just 'Left-Brained'
Bill Bradley, SVP, Cyber Engineering and Technical Services, CenturyLink,  10/17/2017
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
The State of Ransomware
The State of Ransomware
Ransomware has become one of the most prevalent new cybersecurity threats faced by today's enterprises. This new report from Dark Reading includes feedback from IT and IT security professionals about their organization's ransomware experiences, defense plans, and malware challenges. Find out what they had to say!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.