Tip

Mobile app software: Avoid the perpetual cycle of insecurity

Traditional security flaws crop up in mobile app software so often that it seems as if we're intentionally trying to live out Albert Einstein's definition of insanity: Do the same thing time and again but expect different results.

New mobile app software: Same old security flaws

In the past few months security expert Kevin Beaver has spotted the following flaws in mobile apps -- using source code analysis software. He wonders why we are still making the same security mistakes.

  • Code injection: Code injection is an umbrella term for a broad class of attacks including

    Requires Free Membership to View

  • SQL injections, which  depend on inserting code, which is executed by the application.
  • Session fixation: This vulnerability, which lets an attacker hijack a valid user session, is a variant of session hijacking. The session fixation attack fixes an established session on the victim's browser, so the attack starts before the user logs in, according to OWASP.
  • Path traversal: Also known as a "directory traversal," this attack aims to access files and directories that are stored outside the Web root folder, according to OWASP.
  • Weak passwords: Compared with strong passwords, weak passwords have fewer characters and they often lack numbers and special characters. That makes them relatively easy for a password cracker to break.
  • Hard-coded cryptographic keys: Hard-coded cryptographic keys may provide a false sense of security. Some people believe that hashing a hard-coded password before storage protects the information from malicious users. But many hashes are reversible.

In the past few months, using a source code analysis tool, I've uncovered, in both iOS and Android mobile app software, the following, seemingly decades-old security weaknesses:

  • Code injection
  • Session fixation
  • Path traversal
  • Weak passwords
  • Hard-coded cryptographic keys

Any of these sound familiar? These software security problems could literally be taken from textbooks that originated in the 1990s. In fact, some of these concepts go as far back as James Martin's 1973 book titled Security, Accuracy, and Privacy in Computer Systems. Over the past several decades we've evolved from standalone programs to client-server applications to Web applications and now mobile app software. And yet we're still seeing the same old security problems.

So, how can you avoid falling into this perpetual cycle of software insecurities? Here are three actions you can take to strengthen your mobile apps:

  1. Use good source analysis tools to find flaws at the source-code level and improve the overall quality of your mobile application life cycle. With all the demands on your time, it's practically impossible to find everything that matters via old-fashioned manual source code analysis.
  2. Stop relying on tools alone. When you put aside all the technical stuff and simply look at your mobile apps from a malicious user's perspective, you'll likely uncover flaws that are often glaringly obvious and so simple to exploit. The last thing you need is some low-hanging fruit to lead to information exposure or unauthorized system access.
  3. Study the well-established software security flaws documented by OWASP and books such as 24 Deadly Sins of Software Security and ensure everyone on your team is aware of what can go wrong when they don't take their coding seriously enough. Also, keep an eye out for upcoming publications under the OWASP Mobile Security Project and related content such as Security Innovation's Mobile Security Academy that can help you with mobile app-specific issues.

We keep saying the same old things when it comes to mobile app security. I suspect that DevOps nor any other tweak in your mobile ALM process is going to fix these basic coding problems. In fact, today's business demands and information systems complexities will likely make matters worse if you don't somehow focus on software security fundamentals. Left unchecked, these programming flaws will continue in whatever's beyond mobile apps in the years ahead. Resolve to get to the root of the problems in your development and QA processes and be done with this burden once and for all.

Are you doing security testing on mobile apps? Let us know.

This was first published in February 2013

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.