Java Signed Applet Social Engineering Code Execution - Revision history

Eric.freyssinet at 14:46, 8 August 2015

2015-08-08T14:46:43Z

← Older revision		Revision as of 14:46, 8 August 2015
Line 1:		Line 1:
	{{Feature		{{Feature
	\|Description=This exploit dynamically creates a .jar file via the Msf::Exploit::Java mixin, then signs the it. The resulting signed applet is presented to the victim via a web page with an applet tag. The victim's JVM will pop a dialog asking if they trust the signed applet. On older versions the dialog will display the value of CERTCN in the "Publisher" line. Newer JVMs display "UNKNOWN" when the signature is not trusted (i.e., it's not signed by a trusted CA). The SigningCert option allows you to provide a trusted code signing cert, the values in which will override CERTCN. If SigningCert is not given, a randomly generated self-signed cert will be used. Either way, once the user clicks "run", the applet executes with full user permissions.
	\|Link=http://www.rapid7.com/db/modules/exploit/multi/browser/java_signed_applet		\|Link=http://www.rapid7.com/db/modules/exploit/multi/browser/java_signed_applet
	\|FeatureCategory=~~Exploits~~		\|FeatureCategory=Injections
	}}		}}

Eric.freyssinet at 12:15, 19 July 2015

2015-07-19T12:15:05Z

← Older revision		Revision as of 12:15, 19 July 2015
Line 2:		Line 2:
	\|Description=This exploit dynamically creates a .jar file via the Msf::Exploit::Java mixin, then signs the it. The resulting signed applet is presented to the victim via a web page with an applet tag. The victim's JVM will pop a dialog asking if they trust the signed applet. On older versions the dialog will display the value of CERTCN in the "Publisher" line. Newer JVMs display "UNKNOWN" when the signature is not trusted (i.e., it's not signed by a trusted CA). The SigningCert option allows you to provide a trusted code signing cert, the values in which will override CERTCN. If SigningCert is not given, a randomly generated self-signed cert will be used. Either way, once the user clicks "run", the applet executes with full user permissions.		\|Description=This exploit dynamically creates a .jar file via the Msf::Exploit::Java mixin, then signs the it. The resulting signed applet is presented to the victim via a web page with an applet tag. The victim's JVM will pop a dialog asking if they trust the signed applet. On older versions the dialog will display the value of CERTCN in the "Publisher" line. Newer JVMs display "UNKNOWN" when the signature is not trusted (i.e., it's not signed by a trusted CA). The SigningCert option allows you to provide a trusted code signing cert, the values in which will override CERTCN. If SigningCert is not given, a randomly generated self-signed cert will be used. Either way, once the user clicks "run", the applet executes with full user permissions.
	\|Link=http://www.rapid7.com/db/modules/exploit/multi/browser/java_signed_applet		\|Link=http://www.rapid7.com/db/modules/exploit/multi/browser/java_signed_applet
	\|FeatureCategory=~~Exploit~~		\|FeatureCategory=Exploits
	}}		}}

Eric.freyssinet at 12:13, 19 July 2015

2015-07-19T12:13:41Z

← Older revision		Revision as of 12:13, 19 July 2015
Line 1:		Line 1:
	{{Feature		{{Feature
	\|Description=This exploit dynamically creates a .jar file via the Msf::Exploit::Java mixin, then signs the it. The resulting signed applet is presented to the victim via a web page with an applet tag. The victim's JVM will pop a dialog asking if they trust the signed applet. On older versions the dialog will display the value of CERTCN in the "Publisher" line. Newer JVMs display "UNKNOWN" when the signature is not trusted (i.e., it's not signed by a trusted CA). The SigningCert option allows you to provide a trusted code signing cert, the values in which will override CERTCN. If SigningCert is not given, a randomly generated self-signed cert will be used. Either way, once the user clicks "run", the applet executes with full user permissions.[http://www.rapid7.com/db/modules/exploit/multi/browser/java_signed_applet ~~RAPID 7 Metasploit exploit description]~~		\|Description=This exploit dynamically creates a .jar file via the Msf::Exploit::Java mixin, then signs the it. The resulting signed applet is presented to the victim via a web page with an applet tag. The victim's JVM will pop a dialog asking if they trust the signed applet. On older versions the dialog will display the value of CERTCN in the "Publisher" line. Newer JVMs display "UNKNOWN" when the signature is not trusted (i.e., it's not signed by a trusted CA). The SigningCert option allows you to provide a trusted code signing cert, the values in which will override CERTCN. If SigningCert is not given, a randomly generated self-signed cert will be used. Either way, once the user clicks "run", the applet executes with full user permissions.
			\|Link=http://www.rapid7.com/db/modules/exploit/multi/browser/java_signed_applet
	\|FeatureCategory=Exploit		\|FeatureCategory=Exploit
	}}		}}

Eric.freyssinet at 12:09, 19 July 2015

2015-07-19T12:09:31Z

← Older revision		Revision as of 12:09, 19 July 2015
Line 1:		Line 1:
	{{Feature		{{Feature
	\|Description=This exploit dynamically creates a .jar file via the Msf::Exploit::Java mixin, then signs the it. The resulting signed applet is presented to the victim via a web page with an applet tag. The victim's JVM will pop a dialog asking if they trust the signed applet. On older versions the dialog will display the value of CERTCN in the "Publisher" line. Newer JVMs display "UNKNOWN" when the signature is not trusted (i.e., it's not signed by a trusted CA). The SigningCert option allows you to provide a trusted code signing cert, the values in which will override CERTCN. If SigningCert is not given, a randomly generated self-signed cert will be used. Either way, once the user clicks "run", the applet executes with full user permissions.		\|Description=This exploit dynamically creates a .jar file via the Msf::Exploit::Java mixin, then signs the it. The resulting signed applet is presented to the victim via a web page with an applet tag. The victim's JVM will pop a dialog asking if they trust the signed applet. On older versions the dialog will display the value of CERTCN in the "Publisher" line. Newer JVMs display "UNKNOWN" when the signature is not trusted (i.e., it's not signed by a trusted CA). The SigningCert option allows you to provide a trusted code signing cert, the values in which will override CERTCN. If SigningCert is not given, a randomly generated self-signed cert will be used. Either way, once the user clicks "run", the applet executes with full user permissions.[http://www.rapid7.com/db/modules/exploit/multi/browser/java_signed_applet RAPID 7 Metasploit exploit description]

	[http://www.rapid7.com/db/modules/exploit/multi/browser/java_signed_applet RAPID 7 Metasploit exploit description]
	\|FeatureCategory=Exploit		\|FeatureCategory=Exploit
	}}		}}

Eric.freyssinet at 12:08, 19 July 2015

2015-07-19T12:08:56Z

← Older revision		Revision as of 12:08, 19 July 2015
Line 2:		Line 2:
	\|Description=This exploit dynamically creates a .jar file via the Msf::Exploit::Java mixin, then signs the it. The resulting signed applet is presented to the victim via a web page with an applet tag. The victim's JVM will pop a dialog asking if they trust the signed applet. On older versions the dialog will display the value of CERTCN in the "Publisher" line. Newer JVMs display "UNKNOWN" when the signature is not trusted (i.e., it's not signed by a trusted CA). The SigningCert option allows you to provide a trusted code signing cert, the values in which will override CERTCN. If SigningCert is not given, a randomly generated self-signed cert will be used. Either way, once the user clicks "run", the applet executes with full user permissions.		\|Description=This exploit dynamically creates a .jar file via the Msf::Exploit::Java mixin, then signs the it. The resulting signed applet is presented to the victim via a web page with an applet tag. The victim's JVM will pop a dialog asking if they trust the signed applet. On older versions the dialog will display the value of CERTCN in the "Publisher" line. Newer JVMs display "UNKNOWN" when the signature is not trusted (i.e., it's not signed by a trusted CA). The SigningCert option allows you to provide a trusted code signing cert, the values in which will override CERTCN. If SigningCert is not given, a randomly generated self-signed cert will be used. Either way, once the user clicks "run", the applet executes with full user permissions.

	http://www.rapid7.com/db/modules/exploit/multi/browser/java_signed_applet		[http://www.rapid7.com/db/modules/exploit/multi/browser/java_signed_applet RAPID 7 Metasploit exploit description]
	\|FeatureCategory=Exploit		\|FeatureCategory=Exploit
	}}		}}

Eric.freyssinet: Created page with "{{Feature |Description=This exploit dynamically creates a .jar file via the Msf::Exploit::Java mixin, then signs the it. The resulting signed applet is presented to the victim..."

2015-07-19T12:08:20Z

Created page with "{{Feature |Description=This exploit dynamically creates a .jar file via the Msf::Exploit::Java mixin, then signs the it. The resulting signed applet is presented to the victim..."

New page

{{Feature
|Description=This exploit dynamically creates a .jar file via the Msf::Exploit::Java mixin, then signs the it. The resulting signed applet is presented to the victim via a web page with an applet tag. The victim's JVM will pop a dialog asking if they trust the signed applet. On older versions the dialog will display the value of CERTCN in the "Publisher" line. Newer JVMs display "UNKNOWN" when the signature is not trusted (i.e., it's not signed by a trusted CA). The SigningCert option allows you to provide a trusted code signing cert, the values in which will override CERTCN. If SigningCert is not given, a randomly generated self-signed cert will be used. Either way, once the user clicks "run", the applet executes with full user permissions.

http://www.rapid7.com/db/modules/exploit/multi/browser/java_signed_applet
|FeatureCategory=Exploit
}}