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.

Application Security

8/20/2019
12:50 PM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Fintech Startups Get Sloppy With Application Security

Some startups need to shape up or ship out.

British security firm Immuniweb has looked at CB Insights' report entitled "The Fintech 250: The Top Fintech Startups Of 2018" to identify 250 financial tech companies that are still in their early development stages. The report aimed to shed some light on the overall state of web and application security of the fintech companies and compare it with the results of traditional banks.

Immuniweb did similar research on banks which they reported out as "State of Application Security at S&P Global World's 100 Largest Banks," so they do have some experience in analyzing the financial sector.

This time, they come to some sweeping conclusions. For instance, they found 100% of the companies that they looked at have security, privacy and compliance issues related to abandoned or forgotten web applications, APIs and subdomains.

The severity of those issues may vary greatly, with few websites actually failing the tests. A fail would have meant "Exploitable and publicly known security vulnerabilities found."

As far as website security, two main startup websites had the highest "A+" grades both for (1) SSL encryption and (2) website security fully meeting applicable PCI DSS and GDRP compliance requirements. On other websites, Immmuniweb found 64 security issues related to outdated web software or its components. One website had as many as 17 outdated JS libraries and other external software components.

Subdomains were in worse shape for security. There were 2,474 outdated software components across the tested subdomains. The oldest vulnerable CMS is WordPress 4.7.1, with 26 publicly known security issues so far.

SSL/TLS was well implemented by the sites across the board. Only one main website scored with a "B" grade, while all others received "A" or even the highest possible "A+" grades.

But the situation with HTTPS encryption on the subdomains is "alarming," according to Immuniweb. As many as 93 subdomains had the failing "F" grade, and 537 had an untrusted or expired SSL certificate.

GDPR tests were abysmal. As the report says, "64 main websites failed the GDPR compliance test. After vulnerable web software, the second most frequent reason is a missing cookie disclaimer or unset security flags on cookies that transfer tracking, PII or otherwise sensitive information. The third top cause is missing or inaccessible privacy policy." Looks like a lot of work is needed there, and the subdomains as well.

The report looks at fintech's mobile applications too. They found 100% of the mobile applications contained at least one medium-risk security vulnerability, 97% of the mobile applications had two or more medium-risk vulnerabilities, and 3% of the mobile applications contained at least one high-risk security vulnerability. Yikes. While the report offers more detail, the theme stays the same. These startups have to concentrate on their business or they, in time, will lose their customers.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...