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.

Attacks/Breaches

5/28/2019
07:10 PM
50%
50%

FirstAm Leak Highlights Importance of Verifying the Basics

The Fortune 500 giant in the real estate industry missed a basic vulnerability in its website, leaving as many as 885 million sensitive records accessible to attackers. The fix: teaching developers the top 10 security issues and frequent testing.

A simple-to-exploit vulnerability in the website of real estate insurance giant First American Financial that could have resulted in the theft of hundreds of millions of sensitive records underscores the importance of verifying basic security measures and implementing secure programming practices, experts said this week.

The vulnerability, first reported by KrebsOnSecurity, allowed anyone with a valid link to a document on the site to increment the identifier to access the next document in sequence, as processed by the firm. The journalist found that the first record accessible through the site, document 000000075, dated back to 2003.

The basic error is a major misstep for the financial firm. The class of vulnerability is so well known that it had its own slot on the popular Open Web Application Security Project (OWASP) Top 10 list of web security vulnerabilities, "A4-Insecure Direct Object References," for four years, and is so easy to find that a simple Google search often turns up the issue.

"You don't need a sophisticated security solution to find these issues," says Greg Pollock, vice president of products for cloud-security firm UpGuard. "It's not about bulking up on cutting-edge DevOps or continuous integration testing, but back-to-basics engineering practices and having a culture that, if an engineer sees something wrong — and they should have seen something wrong here — they raise the issue and it gets fixed."

Beyond the Top 10
The incident underscores that while many security firms urge customers to "go beyond the OWASP Top 10," a large portion of companies still need to make sure their software developers, application security specialists, and operations teams are meeting basic hurdles. The problem is that developers who do not consider the security implications in the design of their software application may look at a database of millions of records and decide to just index them using a sequential code and, worse, expose that code through the URL in a web application.

"[Y]ou should never expose direct references to your data," Jeff Williams, chief technology officer for Contrast Security, said in a statement on the incident. "Instead, you should always use an indirect reference that only allows access to authorized resources. This takes a bit of extra work, but this is a mandatory part of any internet web application or API."

While there is currently no evidence that anyone accessed the data, the information held by First American is a treasure trove for financial fraudsters and identity thieves. First American is a title insurance company, a critical supplier of information used during the process of selling and buying homes. Title insurance companies collect information from both the buyer and the seller in a real estate transaction, verifying and taking custody of a great deal of sensitive information.

Among the documents that could be accessed through the website were bank account statements, mortgage records, tax information, Social Security numbers, driver's license images, and receipt of money transfers, according to KrebsOnSecurity.

First American acknowledged the vulnerability, calling it "a reported design defect that created the potential for unauthorized access to customer data" in a statement released on May 28.

"We deeply regret the concern this defect has caused," Dennis J. Gilmore, CEO at First American Financial, said in the statement. "We are thoroughly investigating this matter and are fully committed to protecting the security, privacy and confidentiality of the information entrusted to us by our customers."

A real estate developer originally found the issue and reached out to KrebsOnSecurity, which verified the security flaw and contacted First American. After the company had fixed the issue, KrebsOnSecurity published its report.

Although the latest version of the OWASP Top 10, published in 2017, no longer has a category named for the specific class of vulnerabilities, insecure direct object references are one of the two categories that make up a new entry in the top 10 list known as "A5-Broken Access Control."

"Access control weaknesses are common due to the lack of automated detection, and lack of effective functional testing by application developers," OWASP states on its site, adding: "Access control enforces policy such that users cannot act outside of their intended permissions. Failures typically lead to unauthorized information disclosure, modification or destruction of all data, or performing a business function outside of the limits of the user."

Two years ago, most companies had to worry about denial-of-service attacks on their web applications. Today, a wide variety of access control issues dominate the list of cloud security issues, according to the SANS Institute's annual survey. Account or credential hijacking is the top issue, followed by misconfiguration, privileged user abuse, unauthorized application components, and insecure APIs or interfaces, according to the SANS Institute's "2019 State of Cloud Security" report.

Developers need to be knowledgeable about such common issues and create tests to check code for any errors that could undermine security, UpGuard's Pollock says.

"While it is trivial to iterate through and pull out as many documents as you want, the flip side of it — and again why this one has gone undetected so long — is that it is much harder to do mass scans for these direct object references," he says. "Companies need to be mindful that this is a problem [and] have some sort of penetration testing or dynamic testing that looks for data leaks."

Related Content

Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
5/29/2019 | 7:19:11 AM
Respect software developers
Management may have a part in this discussion too.   Outsourcing - writing code can be done from anywhere in the world whether Lincoln, Nebraska or Pune.  It is a damn sight cheaper to do it in Pune and while talented folk do exist in India, all too often it is young and dumb.  Sounds horrible I know but very much true and so companies, to save bucks, hire inexpensive talent wherever they can find them and with limited or no benefit expenses to boot.  Result = poorly written, non-tested code that has holes in it.  Thousand of miles away also removes true group participation with a time difference thrown in.  Whether overseas or domestic staff, talent should be good if not excellent on certain IT functions.  Now I am not surprised by this for look how many talented IT staffers in THIS country miss BACKUP PROTOCOLS, DISASTER RECOVERY PROCEDURES and BUSINESS CONTINUITY PLANNING.  How can you then expect true quality work from anybody if WE miss out on the basics.  Forget the advanced stuff - we're dead at the starting line. 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/29/2019 | 8:36:12 AM
Re: Respect software developers
Outsourcing - writing code can be done from anywhere in the world whether Lincoln, Nebraska or Pune. I think it is less about where you code more about how you code.
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
5/29/2019 | 8:46:36 AM
Re: Respect software developers
TRUE and it is the quality of coding that is the point - I may be jaded but my experience with India in general, not specific, has been less than quality folk.  I have dealt with wonderful experts who are great people --- all too few and far between alas.  I just don't see real quality work coming out of Bangalore most of the time.  Freshers, people with NEW degrees, also lack experience --- and whether HERE OR OVER THERE.  
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/29/2019 | 8:37:40 AM
Re: Respect software developers
to save bucks, hire inexpensive talent wherever they can find them and with limited or no benefit expenses to boot. This makes sense, we need skills to do good secure coding.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/29/2019 | 8:38:51 AM
Re: Respect software developers
Result = poorly written, non-tested code that has holes in it. Agree. That is why we need a testing phase to find all the bugs and fix them.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/29/2019 | 8:40:28 AM
Re: Respect software developers
How can you then expect true quality work from anybody if WE miss out on the basics. Forget the advanced stuff - we're dead at the starting line. This really makes sense. Basics have to be covered first, if not it does not matter what else you do.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/29/2019 | 8:35:12 AM
Basics
First American Financial that could have resulted in the theft of hundreds of millions of sensitive records underscores the importance of verifying basic security measures and implementing secure programming practices, experts said this week. If they could not do basics they should not be in the business of holding others data.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9079
PUBLISHED: 2020-08-11
FusionSphere OpenStack 8.0.0 have a protection mechanism failure vulnerability. The product incorrectly uses a protection mechanism. An attacker has to find a way to exploit the vulnerability to conduct directed attacks against the affected product.
CVE-2020-16275
PUBLISHED: 2020-08-10
A cross-site scripting (XSS) vulnerability in the Credential Manager component in SAINT Security Suite 8.0 through 9.8.20 could allow arbitrary script to run in the context of a logged-in user when the user clicks on a specially crafted link.
CVE-2020-16276
PUBLISHED: 2020-08-10
An SQL injection vulnerability in the Assets component of SAINT Security Suite 8.0 through 9.8.20 allows a remote, authenticated attacker to gain unauthorized access to the database.
CVE-2020-16277
PUBLISHED: 2020-08-10
An SQL injection vulnerability in the Analytics component of SAINT Security Suite 8.0 through 9.8.20 allows a remote, authenticated attacker to gain unauthorized access to the database.
CVE-2020-16278
PUBLISHED: 2020-08-10
A cross-site scripting (XSS) vulnerability in the Permissions component in SAINT Security Suite 8.0 through 9.8.20 could allow arbitrary script to run in the context of a logged-in user when the user clicks on a specially crafted link.