Security/Reviews/AppStore - Revision history

Gdestuynder: Added threat 8

2013-03-13T21:45:27Z

Added threat 8

← Older revision		Revision as of 21:45, 13 March 2013
Line 112:		Line 112:
	\|-		\|-
	\| 7\|\|CSRF could force purchase. \|\|If a XSS is found in the marketplace, this could be used to force a purchase. \|\|A PIN is to be implemented that is required for purchases and in-app purchases. enable CSRF protection token on the marketplace site. CEF logging on transactions to track excessive purchases. Incident response to deal with stolen credentials. Paypal account shows all purchases. \|\|Malicious App\|\|12\|\|3\|\|4 – Reputation\|\|		\| 7\|\|CSRF could force purchase. \|\|If a XSS is found in the marketplace, this could be used to force a purchase. \|\|A PIN is to be implemented that is required for purchases and in-app purchases. enable CSRF protection token on the marketplace site. CEF logging on transactions to track excessive purchases. Incident response to deal with stolen credentials. Paypal account shows all purchases. \|\|Malicious App\|\|12\|\|3\|\|4 – Reputation\|\|
			\|-
			\| 8\|\|Compromise AMO web-heads \|\|An attacker able to run arbitrary code on the AMO web-heads can indirectly sign arbitrary web applications that are in the review queue (any web application that passed the automated scan) via the celery service. The attacker can also directly sign a web application by requesting the signing from the signing service, without any further check.\|\|Mitigation possibilities are being discussed.\|\|System access\|\|12\|\|3\|\|4 – Reputation\|\|
	\|-		\|-
	\|}		\|}

Rforbes: /* Threat Model */

2013-01-03T08:38:13Z

Threat Model

← Older revision		Revision as of 08:38, 3 January 2013
Line 98:		Line 98:
	\| align="center" style="background:#f0f0f0;"\|'''Notes'''		\| align="center" style="background:#f0f0f0;"\|'''Notes'''
	\|-		\|-
	\| 1\|\|Compromise Paypal API Key\|\|The Paypal API key is used for communication with paypal and identifies Mozilla. If this key is leaked, it is possible to impersonate Mozilla to Paypal.\|\|Separation of payment systems from the rest of AMO. Incident response process to include communication with payal to disable API key. Proper CEF logging key.\|\|Skilled Attacker\|\|12\|\|3\|\|4 – Reputation\|\|
	\|-		\|-
	\| 2\|\|Compromise AMO database\|\|Currently, customer's paypal information resides in the AMO database. If the AMO database is compromised this would include paypal information.\|\|Separation of payment data from the rest of AMO. Incident response process to include communication with payal to disable pre-auth keys. Proper CEF logging key.\|\|Skilled Attacker\|\|12\|\|3\|\|4 – Reputation\|\|for an actual compromise, this would require the paypal API key as well.		\| 1\|\|Compromise AMO database\|\|Currently, customer's paypal information resides in the AMO database. If the AMO database is compromised this would include paypal information.\|\|Separation of payment data from the rest of AMO. Incident response process to include communication with payal to disable pre-auth keys. Proper CEF logging key.\|\|Skilled Attacker\|\|12\|\|3\|\|4 – Reputation\|\|for an actual compromise, this would require the paypal API key as well.
	\|-		\|-
	\| 3\|\|malicious access to apps device \|\|If a phone is stolen or given to a friend/family member, it is possible for that person to make purchases.\|\|A PIN is to be implemented that is required for purchases and in-app purchases. CEF logging on transactions to track excessive purchases. Incident response to deal wiht stolen phone.\|\|Malicious User\|\|12\|\|3\|\|4 – Reputation\|\|In other systems (i.e. iOS, this i a configured parameter.		\| 2\|\|malicious access to apps device \|\|If a phone is stolen or given to a friend/family member, it is possible for that person to make purchases.\|\|A PIN is to be implemented that is required for purchases and in-app purchases. CEF logging on transactions to track excessive purchases. Incident response to deal wiht stolen phone.\|\|Malicious User\|\|12\|\|3\|\|4 – Reputation\|\|In other systems (i.e. iOS, this i a configured parameter.
	\|-		\|-
	\| 4\|\|Malicious extension could steal browserid credentials \|\|A rogue extension could possibly steal credentials or cause transactions to happen.\|\|A PIN is to be implemented that is required for purchases and in-app purchases. CEF logging on transactions to track excessive purchases. Incident response to deal with stolen credentials.\|\|Malicious Developer\|\|12\|\|3\|\|4 – Reputation\|\|It is not possible to siphon funds to any paypal account. Must be registered with marketplace.		\| 3\|\|Malicious extension could steal browserid credentials \|\|A rogue extension could possibly steal credentials or cause transactions to happen.\|\|A PIN is to be implemented that is required for purchases and in-app purchases. CEF logging on transactions to track excessive purchases. Incident response to deal with stolen credentials.\|\|Malicious Developer\|\|12\|\|3\|\|4 – Reputation\|\|It is not possible to siphon funds to any paypal account. Must be registered with marketplace.
			\|-
			\| 4\|\|Malicious App creates fake iframe \|\|An app could create an iframe in order to overlay a purchase iframe. \|\|A PIN is to be implemented that is required for purchases and in-app purchases. CEF logging on transactions to track excessive purchases. Incident response to deal with stolen credentials. Paypal account shows all purchases. \|\|Malicious App\|\|12\|\|3\|\|4 – Reputation\|\|
	\|-		\|-
	\| 5\|\|Malicious App creates fake iframe \|\|An app could create an iframe in order to overlay a purchase iframe. \|\|A PIN is to be implemented that is required for purchases and in-app purchases. CEF logging on transactions to track excessive purchases. Incident response to deal with stolen credentials. Paypal account shows all purchases. \|\|Malicious App\|\|12\|\|3\|\|4 – Reputation\|\|		\| 5\|\|Malicious App creates fake iframe \|\|An app could create an iframe in order to overlay a purchase iframe. \|\|A PIN is to be implemented that is required for purchases and in-app purchases. CEF logging on transactions to track excessive purchases. Incident response to deal with stolen credentials. Paypal account shows all purchases. \|\|Malicious App\|\|12\|\|3\|\|4 – Reputation\|\|
	\|-		\|-
	\| 6\|\|Malicious App creates fake iframe \|\|An app could create an iframe in order to overlay a purchase iframe. \|\|A PIN is to be implemented that is required for purchases and in-app purchases. CEF logging on transactions to track excessive purchases. Incident response to deal with stolen credentials. Paypal account shows all purchases. \|\|Malicious App\|\|12\|\|3\|\|4 – Reputation\|\|		\| 6\|\|XSS vuln could allow malicious user to force purchase \|\|If a XSS is found in the marketplace, this could be used to force a purchase. \|\|A PIN is to be implemented that is required for purchases and in-app purchases. enable CSP on the marketplace site. CEF logging on transactions to track excessive purchases. Incident response to deal with stolen credentials. Paypal account shows all purchases. \|\|Malicious App\|\|12\|\|3\|\|4 – Reputation\|\|
	\|-
	~~\| 7~~\|\|XSS vuln could allow malicious user to force purchase \|\|If a XSS is found in the marketplace, this could be used to force a purchase. \|\|A PIN is to be implemented that is required for purchases and in-app purchases. enable CSP on the marketplace site. CEF logging on transactions to track excessive purchases. Incident response to deal with stolen credentials. Paypal account shows all purchases. \|\|Malicious App\|\|12\|\|3\|\|4 – Reputation\|\|
	\|-		\|-
	\| 8\|\|CSRF could force purchase. \|\|If a XSS is found in the marketplace, this could be used to force a purchase. \|\|A PIN is to be implemented that is required for purchases and in-app purchases. enable CSRF protection token on the marketplace site. CEF logging on transactions to track excessive purchases. Incident response to deal with stolen credentials. Paypal account shows all purchases. \|\|Malicious App\|\|12\|\|3\|\|4 – Reputation\|\|		\| 7\|\|CSRF could force purchase. \|\|If a XSS is found in the marketplace, this could be used to force a purchase. \|\|A PIN is to be implemented that is required for purchases and in-app purchases. enable CSRF protection token on the marketplace site. CEF logging on transactions to track excessive purchases. Incident response to deal with stolen credentials. Paypal account shows all purchases. \|\|Malicious App\|\|12\|\|3\|\|4 – Reputation\|\|
	\|-		\|-
	\|}		\|}

Rforbes: /* Data Flows */

2012-12-02T09:24:46Z

Data Flows

← Older revision		Revision as of 09:24, 2 December 2012
Line 80:		Line 80:
	[https://wiki.mozilla.org/Apps/ID_and_Payments#Payments_Data_Flow_Diagram Data Flow Diagrams]		[https://wiki.mozilla.org/Apps/ID_and_Payments#Payments_Data_Flow_Diagram Data Flow Diagrams]

	==== Data ~~Types~~ ====		==== Data Type Definition ====
	[https://wiki.mozilla.org/Apps/ID_and_Payments#Payments_Data_Types Data Types]		[https://wiki.mozilla.org/Apps/ID_and_Payments#Payments_Data_Types Data Types]

Rforbes: /* Stage 1: Definition */

2012-12-02T09:24:13Z

Stage 1: Definition

← Older revision		Revision as of 09:24, 2 December 2012
Line 79:		Line 79:
	==== Diagram ====		==== Diagram ====
	[https://wiki.mozilla.org/Apps/ID_and_Payments#Payments_Data_Flow_Diagram Data Flow Diagrams]		[https://wiki.mozilla.org/Apps/ID_and_Payments#Payments_Data_Flow_Diagram Data Flow Diagrams]

			==== Data Types ====
			[https://wiki.mozilla.org/Apps/ID_and_Payments#Payments_Data_Types Data Types]

	== Stage 2: Design ==		== Stage 2: Design ==

Rforbes: /* Diagram */

2012-12-01T08:21:20Z

Diagram

← Older revision		Revision as of 08:21, 1 December 2012
Line 78:		Line 78:

	==== Diagram ====		==== Diagram ====
	[https://wiki.mozilla.org/Apps/ID_and_Payments#~~Developer_Registration_Data_Flow_Diagram~~ Data Flow Diagrams]		[https://wiki.mozilla.org/Apps/ID_and_Payments#Payments_Data_Flow_Diagram Data Flow Diagrams]

	== Stage 2: Design ==		== Stage 2: Design ==

Rforbes: /* Diagram */

2012-12-01T08:19:26Z

Diagram

← Older revision		Revision as of 08:19, 1 December 2012
Line 78:		Line 78:

	==== Diagram ====		==== Diagram ====
	[https://wiki.mozilla.org/Apps/ID_and_Payments#Developer_Registration_Data_Flow_Diagram]		[https://wiki.mozilla.org/Apps/ID_and_Payments#Developer_Registration_Data_Flow_Diagram Data Flow Diagrams]

	== Stage 2: Design ==		== Stage 2: Design ==

Rforbes: /* Data Flows */

2012-12-01T08:18:45Z

Data Flows

← Older revision		Revision as of 08:18, 1 December 2012
Line 78:		Line 78:

	==== Diagram ====		==== Diagram ====
			[https://wiki.mozilla.org/Apps/ID_and_Payments#Developer_Registration_Data_Flow_Diagram]

	== Stage 2: Design ==		== Stage 2: Design ==

Rforbes: /* Architecture Diagram */

2012-12-01T08:18:18Z

Architecture Diagram

← Older revision		Revision as of 08:18, 1 December 2012
Line 78:		Line 78:

	==== Diagram ====		==== Diagram ====

	~~=== Architecture Diagram ===~~

	== Stage 2: Design ==		== Stage 2: Design ==

Rforbes: /* Data Types */

2012-12-01T08:17:54Z

Data Types

@@ Line 74: / Line 74: @@
 === Use Cases ===
 [https://wiki.mozilla.org/Apps#Published_docs Published Docs]
 === Data Flows ===

Rforbes: /* Diagram */

2012-12-01T08:13:28Z

Diagram

← Older revision		Revision as of 08:13, 1 December 2012
Line 148:		Line 148:

	==== Diagram ====		==== Diagram ====
	~~[[file:Appstore_purchase_dfd.png]]~~
	~~[[file:pre-auth.jpg]]~~
	~~[[file:In-app payments.jpg]]~~

	=== Architecture Diagram ===		=== Architecture Diagram ===