cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kerrishotts <>
Subject [GitHub] cordova-docs pull request #703: CB-12770: revise security documentation
Date Mon, 08 May 2017 21:29:00 GMT
Github user kerrishotts commented on a diff in the pull request:
    --- Diff: www/docs/en/dev/guide/appdev/security/ ---
    @@ -27,69 +27,155 @@ description: Information and tips for building a secure application.
     The following guide includes some security best practices that you should consider when
developing a Cordova application. Please be aware that security is a very complicated topic
and therefore this guide is not exhaustive. If you believe you can contribute to this guide,
please feel free to file an issue in Cordova's bug tracker under ["Documentation"](
 This guide is designed to be applicable to general Cordova development (all platforms) but
special platform-specific considerations will be noted.
     ## This guide discusses the following topics:
    +* General Tips
    +* Plugins and Security
    +* Content Security Policy
     * Whitelist
    -* Iframes and the Callback Id Mechanism
     * Certificate Pinning
     * Self-signed Certificates
    +* Wrapping external sites and hot code push
     * Encrypted storage
    -* General Tips
     * Recommended Articles and Other Resources
    +## General Tips
    +### Use InAppBrowser for outside links
    +Use the InAppBrowser when opening links to any outside website. This is much safer than
whitelisting a domain name and including the content directly in your application because
the InAppBrowser will use the native browser's security features and will not give the website
access to your Cordova environment. Even if you trust the third party website and include
it directly in your application, that third party website could link to malicious web content.
    +### Validate all user input
    +Always validate any and all input that your application accepts. This includes usernames,
passwords, dates, uploaded media, etc. Because an attacker could manipulate your HTML and
JS assets (either by decompiling your application or using debugging tools like `chrome://inspect`),
this validation should also be performed on your server, especially before handing the data
off to any backend service.
    +> **Tip**: Other sources where data should be validated: user documents, contacts,
push notifications
    +### Do not cache sensitive data
    +If usernames, password, geolocation information, and other sensitive data is cached,
then it could potentially be retrieved later by an unauthorized user or application.
    --- End diff --
    Yes, this needs to be worded better and have some concrete examples. :-) I think "caching"
is the wrong word here (this was copied from the previous version) -- "store" is probably
more accurate.
    I _think_ attacks would either have to be device-in-hand attacks (since you'd need to
get into the file system -- that's when you hope the device is protected with a pin &
is encrypted!) or malware / viruses that abused some security hole (or ran amuck on a rooted/JB'd
device). OR, if the app stored data in a public area on the file system (say, on Android),
that would be risky too. (Hopefully no one would do that, though...!) So yes... more examples
of what is meant by this would be good.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message