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.

Endpoint

8/9/2019
04:45 PM
50%
50%

State Farm Reports Credential-Stuffing Attack

The insurer has informed customers a third party used a list of user IDs and passwords to attempt access into online accounts.

US insurance firm State Farm has confirmed a credential-stuffing attack. In a letter to customers, the company reports a so-called "bad actor" used a list of user IDs and passwords obtained from outside sources to attempt to gain access to State Farm online accounts.

As part of the attack, the actor was able to confirm a valid username and password for affected accounts. No sensitive personal information was viewable, State Farm says, and no fraud has been detected. It has reset passwords to block future malicious activity by the same attacker.

In its notification letter, the insurer urges users to change passwords as soon as possible and to reset the password for other accounts that share the same one. Customers are encouraged to monitor their accounts and credit reports for the next one to two years and report suspicious activity to law enforcement, including the Federal Trade Commission and attorney general.

Read more details here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
tdsan
50%
50%
tdsan,
User Rank: Ninja
8/10/2019 | 4:37:38 PM
It may be time to take things into their own hands, if not them, then who?

"As already implied, unique username and password combinations are indeed the number one way to mitigate the effectiveness of credential-stuffing attacks," he said via email. "However, the burden of creating and maintaining these unique combinations falls on the shoulders of the proverbial "weakest link" (i.e., the end user). It may be time for organizations to take matters into their own hands though. If end users can't or won't comply with the guidance being provided to keep their accounts safe"

 Interesting comment, if they don't do it, then the FTC will do it by handing down fines in the form of punitive damages to customers. They should use MFA using TOTP (Time-Based Ontime Passcodes) or HTOP (Hmac-Based Ontime Based Passcodes), they could associate this one time passcode to the customer's phone so if they need to login to the site, the companies could set-up a method to send a 6-digit code to their phone or a randomly generated code could be a security feature that allows the user to check their insurance status.

Also, they could add complexity to the passwords like at least 1 upper, 1 lower, 1 number, and 1 special character; they could even add limits to the number of times a person tries a password until they have to call customer service to have their account unlocked.

Password Complexity

A lot of companies are doing this, I guess it took a potential breach or possible compromise for the organization to take notice. The existing methods are not working anymore, we need to combine MFA, complexity and TOTP/HTOP to address this issue because computers are getting faster and faster, hopefully State Farm is looking into that.

 
  • (72 x 10)^14 = 72 x 10 to the 14th power, not the mention a 30 sec 6 digit code that rotates is the statistical function used to calculate the number of times a computer would have to guess a users password (if they have proper controls, it would not allow them to anymore after 6 attempts).

Just a word to the wise.

T

 
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Look Beyond the 'Big 5' in Cyberattacks
Robert Lemos, Contributing Writer,  11/25/2020
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: We are really excited about our new two tone authentication system!
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15257
PUBLISHED: 2020-12-01
containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that...
CVE-2020-9114
PUBLISHED: 2020-12-01
FusionCompute versions 6.3.0, 6.3.1, 6.5.0, 6.5.1 and 8.0.0 have a privilege escalation vulnerability. Due to improper privilege management, an attacker with common privilege may access some specific files and get the administrator privilege in the affected products. Successful exploit will cause pr...
CVE-2020-9117
PUBLISHED: 2020-12-01
HUAWEI nova 4 versions earlier than 10.0.0.165(C01E34R2P4) and SydneyM-AL00 versions earlier than 10.0.0.165(C00E66R1P5) have an out-of-bounds read and write vulnerability. An attacker with specific permissions crafts malformed packet with specific parameter and sends the packet to the affected prod...
CVE-2020-4126
PUBLISHED: 2020-12-01
HCL iNotes is susceptible to a sensitive cookie exposure vulnerability. This can allow an unauthenticated remote attacker to capture the cookie by intercepting its transmission within an http session. Fixes are available in HCL Domino and iNotes versions 10.0.1 FP6 and 11.0.1 FP2 and later.
CVE-2020-4129
PUBLISHED: 2020-12-01
HCL Domino is susceptible to a lockout policy bypass vulnerability in the LDAP service. An unauthenticated attacker could use this vulnerability to mount a brute force attack against the LDAP service. Fixes are available in HCL Domino versions 9.0.1 FP10 IF6, 10.0.1 FP6 and 11.0.1 FP1 and later.