This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Architecture and design principles

From OWASP
Revision as of 12:15, 10 May 2011 by Giles Hogben (talk | contribs)

Jump to: navigation, search

The following is a merge of ENISA, OWASP and Veracode top 10. Note that there is a mixture of threats and vulnerabilities here - we should decide whether to use risks (threats with impact on assets which occur with probability) and vulnerabilities (system flaws which increase the probability of a threat occurring). I have cut those risks/vulnerabilities which cannot be addressed in any way by developers. We should decide whether to include recommendations in the style of "code of practice"- e.g. activity monitoring should only be used in circumstances xyz...

Top Risks/Vulnerabilities

  1. Unsafe sensitive data storage
  2. Unintentional disclosure of data: The smartphone user unintentionally discloses data on the smartphone.
  3. Attacks on decommissioned smartphones: The smartphone is decommissioned improperly allowing an attacker access to the data on the device.
  4. Phishing attacks: An attacker collects user credentials (such as passwords and credit card numbers) by means of fake apps or (SMS, email) messages that seem genuine.
  5. Spyware: Spyware covers untargeted collection of personal information as opposed to targeted surveillance.
  6. Network Spoofing Attacks: An attacker deploys a rogue network access point (WiFi or GSM) and users connect to it. The attacker subsequently intercepts (or tampers with) the user communication to carry out further attacks such as phishing.
  7. Surveillance attacks: An attacker keeps a specific user under surveillance through the target user’s smartphone.
  8. Diallerware attacks: An attacker steals money from the user by means of malware that makes hidden use of premium SMS services or numbers.
  9. Financial malware attacks The smartphone is infected with malware specifically designed for stealing credit card numbers, online banking credentials or subverting online banking or ecommerce transactions.
  10. Network congestion Network resource overload due to smartphone usage leading to network unavailability for the end-user.
  11. Unauthorized network connectivity (exfiltration or command & control)
  12. UI Impersonation
  13. System modification (rootkit, APN proxy config)
  14. Logic or Time bomb (including runtime interpreter)
  15. Unsafe sensitive data transmission
  16. Hardcoded password/keys
  17. Lack of data protection in transit
  18. Client-side injection
  19. Client-side DOS
  20. Malicious third-party code
  21. Client-side buffer overflow
  22. Failure to properly handle inbound SMS messages
  23. Failure to properly handle outbound SMS messages
  24. Failure to disable insecure platform features in application (caching of keystrokes, screen data)