Application Security

8/7/2018
05:45 PM
Connect Directly
Twitter
Twitter
RSS
E-Mail
100%
0%

Expect API Breaches to Accelerate

APIs provide the digital glue that binds apps, cloud resources, app services and data all together - and they're increasingly an appsec security threat.

Last year the category of underprotected APIs cracked the OWASP Top 10 list for the first time. The breach trends since then are starting to prove that inclusion was pretty prescient. Just in 2018 alone we've seen at least half a dozen high-profile data breaches and security exposures caused by poor API security. And that doesn’t even include incidents last year at T-Mobile, Instagram, and McDonalds that all together exposed sensitive data about millions of their users. 

This week the latest API security incident to make waves struck Salesforce, which reported to customers that a bug in an API in its Marketing Cloud service potentially exposed customer data. The flaw could have caused API calls to retrieve or write data from one customer's account to another's, the company stated

This is a different verse of the same song we continue to hear about the growing trend of API insecurity. Just last month, for example, researchers announced that mobile payment app Venmo has been exposing details about hundreds of millions of transactions through a poorly secured API. And this spring an egregiously insecure Panera Bread API exposed details about mobile users in a major way. In that case, as many as 37 million records, including customer names, email addresses, physical addresses, birthdays, and the last four digits of credit cards — all in plain text — were exposed through a searchable API that required no authentication to access.

This is an issue that cuts across all company sizes and industries. Last month, for example, HIMSS released a report showing that exploitation of API flaws has become a major concern for healthcare organizations. And a study earlier this year by Imperva showed that more than two-thirds of organizations expose APIs to the public in order to enable partners and external developers to tap into their software platforms and app ecosystems. Unfortunately, more than three in four organizations report they treat API security differently than Web app security — indicating that API security readiness lags behind other aspects of application security.

That Imperva study also shows how prevalent API use is becoming within most organizations: The typical organization now manages an average of 363 APIs. This can be chalked up to a growing trend in the development world toward microservices, where most modern applications are no longer monolithic pieces of software but are instead composed of smaller components that can be reused, mixed, and matched across an entire application portfolio.

In addition, whole application ecosystems depend on open connectivity to share data and make users' lives easier through better integrations. APIs are what's used to help all of these components play nicely together and to get applications seamlessly sharing data among themselves. Indeed, 61% of organizations say API integration is critical to their business strategy.

"In 2018, it is expected that you need APIs to do business in this digital age," writes Kin Lane, who's known as the API evangelist at Cloud Elements. "The companies, organizations, institutions, and government agencies who are just beginning to invest in their API infrastructure are quickly realizing how far behind they are when it comes to the efficient delivery of data and content to Web and mobile applications, as well as the ability to work with Internet-connected devices, and take advantage of the benefits of machine learning and artificial intelligence."

But as businesses jump on the API development trend, they'll need to keep in mind that the more APIs grow in importance to them, the more they will grow in importance t attackers. According to Gartner, by 2022 API abuses will be the attack vector most responsible for data breaches within enterprise Web applications. 

Related Content:

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Australian Teen Hacked Apple Network
Dark Reading Staff 8/17/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-15504
PUBLISHED: 2018-08-18
An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2. The server mishandles some HTTP request fields associated with time, which results in a NULL pointer dereference, as demonstrated by If-Modified-Since or If-Unmodified-Since with a month greater than 11.
CVE-2018-15505
PUBLISHED: 2018-08-18
An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2. An HTTP POST request with a specially crafted "Host" header field may cause a NULL pointer dereference and thus cause a denial of service, as demonstrated by the lack of a trailing ']' character in an IPv6 a...
CVE-2018-15492
PUBLISHED: 2018-08-18
A vulnerability in the lservnt.exe component of Sentinel License Manager version 8.5.3.35 (fixed in 8.5.3.2403) causes UDP amplification.
CVE-2018-15494
PUBLISHED: 2018-08-18
In Dojo Toolkit before 1.14, there is unescaped string injection in dojox/Grid/DataGrid.
CVE-2018-15495
PUBLISHED: 2018-08-18
/filemanager/upload.php in Responsive FileManager before 9.13.3 allows Directory Traversal and SSRF because the url parameter is used directly in a curl_exec call, as demonstrated by a file:///etc/passwd value.