Alpha Generation Distribution Ltd is a 4SEC Group Company
Follow us on Twitter Follow us on LinkedIn
Call us on: 01777 852222

Critical Application Vulnerabilities You Haven’t Read About

Critical Vulnerabilities You Haven’t Read About

The issue used to be understanding that applications could be vulnerable. Today, you know that attackers can exploit your software to gain wider system access.

That’s largely in part to headline incidents where major application vulnerabilities were discovered in common applications. From VENOM to Code Red to Heartbleed, more and more vulnerabilities are picked up by specialist media. Some of the biggest even manage to hit mainstream press.

But while knowing that vulnerabilities pose a huge danger is a good start, it’s actually not that useful. It just leads to a bigger question – what on earth do I do now?

When application vulnerabilities hit the big time

Forget celebrities and footballers – the mainstream press is increasingly concerned with our network security. After all, we’re in a world where everything is connected. From phones to thermostats to fridges, the Internet of Things means everything can be networked.

And in a digital age, digital crime is just as important as any other form.

Take ShellShock. In 2014, open source software developer Stephane Chazelas discovered a bug in the Unix Bash shell that could be exploited to run arbitrary code. As a result, people could execute malicious commands on any device where Bash is used – everything from Linux web servers to Apple laptops and smartphones.

Having gone unnoticed in Bash since 1993, this was big news. So when Chazeles disclosed the bug he had uncovered, it was detailed everywhere from specialist IT security websites to The Huffington Post and The Guardian.

With even a cursory eye on the latest news, you couldn’t help but know about ShellShock. So it was easy to get to work, investigating where Bash was present across your network and applying the relevant patches.

But, widely reported, ShellShock was the exception to the rule.

Meet CVE-2015-0332

Adobe Flash Player/AIR Multiple VulnerabilitiesYou’re probably familiar with ShellShock. You can’t have missed Heartbleed. But without celebrity status, CVE-2015-0332 hasn’t hit the headlines.

Despite a less catchy name, this application vulnerability is serious. It affects Adobe Flash Player and Adobe Air – popular, commonplace applications that most of us are running.

According to Secunia’s detailed vulnerability advisory, this application vulnerability relates to a series of exploits that could be used to corrupt memory, and then used to run arbitrary code.

Like ShellShock before it, CVE-2015-0332 represents a huge risk. Thankfully, it’s easily fixed with an update to the latest Adobe Flash Player and Adobe Air versions.

But CVE-2015-0332 hasn’t been reported. The Guardian hasn’t given it a glance. The Huffington Post hasn’t posted.

So how can you expect to know about the latest application vulnerabilities as soon as they happen, let alone resolve them quickly?

How do you check for critical application vulnerabilities?

The security community has a collaborative approach to disclosing and logging all application vulnerabilities as they’re discovered. Meanwhile, most reputable software vendors aim to keep customers informed.

So, to keep up with the latest application vulnerabilities, you could:

  • Use an open source application vulnerability database – manually checking every application you use for vulnerabilities. But how often? Every month? Every week? Every day? Every hour?
  • Sign up for updates from every third-party software vendor you use – and trust that they’ll keep you updated about vulnerabilities as soon as they happen

The problem is that this doesn’t leave a lot of time for everything else you need to do. Staying on top of application vulnerabilities requires a significant investment of time.

And even if you can spare the time, this approach depends on a 100% accurate view of all the third-party software that’s installed across your entire network.