Vodafone's BreachA Painful Lesson In Shared Passwords

Vodafone's embarrassing breach should serve as a wake-up call for enterprises that also engage in the dangerous practice of credential-sharing

The Australian operation of the wireless carrier Vodafone is feeling the full range of consequences from an information security breach--from notifying customers to firing employees to facing down regulators. And it's all because of a common but unsafe practice: Allowing shared passwords within enterprise accounts.

Vodafone officials were red-faced in January when they were informed by a journalist that she was able to log into the carrier's customer database using legitimate credentials. Australian Privacy Commissioner Timothy Pilgrim announced an investigation into the breach, and Vodafone warned customers of the problem and fired a number of employees in connection with the matter.

Vodafone said it acted quickly to shut down improper access. CEO Nigel Dews assured the public that Vodafone had changed passwords across the board and implemented more stringent password policies, including more frequent changes.

Account credential sharing is hardly a one-off problem in any big company, says Adam Bosnian, executive VP with Cyber-Ark Software, a security vendor. He's seen it most in retail environments, if turnover's high and there's no easy way to create and delete accounts when people join or leave the company. So companies take the efficient but "inherently risky" approach of just using generic, shared accounts, he says.

Password sharing can be particularly troublesome with databases accessed by Web applications, such as the one that powers Internet access to Vodafone's customer database, warns Phil Lieberman, CEO of Lieberman Software. "What happens is that there are certain high-powered accounts that are used by applications and also by users--call them 'generic accounts' because they end up being shared," he says.

One problem with such an account is there's no audit trail--you don't know if an app automatically accessed it, or a particular person did. Too many companies allow the practice to continue. IT staff in other companies could face the same fate as those at Vodafone who were fired should their sloppy practices be exposed.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Government Shutdown Brings Certificate Lapse Woes
Curtis Franklin Jr., Senior Editor at Dark Reading,  1/11/2019
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. Because of a bug in ctl_getitem, there is a stack-based buffer over-read in read_sysvars in ntp_control.c in ntpd.
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. process_control() in ntp_control.c has a stack-based buffer over-read because attacker-controlled data is dereferenced by ntohl() in ntpd.
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. An authenticated attacker can cause a NULL pointer dereference and ntpd crash in ntp_control.c, related to ctl_getitem.
PUBLISHED: 2019-01-16
An issue was discovered in NumPy 1.16.0 and earlier. It uses the pickle Python module unsafely, which allows remote attackers to execute arbitrary code via a crafted serialized object, as demonstrated by a numpy.load call.
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. An authenticated attacker can write one byte out of bounds in ntpd via a malformed config request, related to config_remotely in ntp_config.c, yyparse in ntp_parser.tab.c, and yyerror in ntp_parser.y.