-
Bug
-
Resolution: Fixed
-
P3
-
None
-
b89
-
os_x
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8142591 | emb-9 | Chris Bensen | P3 | Resolved | Fixed | team |
JDK-8168221 | 8u152 | David Dehaven | P3 | Resolved | Fixed | b01 |
JDK-8163617 | 8u121 | David Dehaven | P3 | Resolved | Fixed | b01 |
JDK-8159471 | 8u112 | David Dehaven | P3 | Resolved | Fixed | b01 |
JDK-8160588 | 8u111 | David Dehaven | P3 | Resolved | Fixed | b03 |
JDK-8160582 | 8u102 | David Dehaven | P3 | Resolved | Fixed | b31 |
JDK-8160497 | 8u92 | David Dehaven | P3 | Resolved | Fixed | b34 |
JDK-8167711 | emb-8u121 | David Dehaven | P3 | Resolved | Fixed | b01 |
JDK-8162045 | emb-8u111 | David Dehaven | P3 | Resolved | Fixed | b03 |
In AppDelegate.m change the call to system to either NSTask or execv. URLs could have spaces which would be a potential vulnerability. Here is an example of NSTask:
NSTask *task = [[NSTask alloc] init];
task.launchPath = @"/Library/Internet\\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/javaws";
task.arguments = @[url];
[task launch];
- backported by
-
JDK-8142591 Change JavawsLauncher.app to use NSTask or execv
- Resolved
-
JDK-8159471 Change JavawsLauncher.app to use NSTask or execv
- Resolved
-
JDK-8160497 Change JavawsLauncher.app to use NSTask or execv
- Resolved
-
JDK-8160582 Change JavawsLauncher.app to use NSTask or execv
- Resolved
-
JDK-8160588 Change JavawsLauncher.app to use NSTask or execv
- Resolved
-
JDK-8162045 Change JavawsLauncher.app to use NSTask or execv
- Resolved
-
JDK-8163617 Change JavawsLauncher.app to use NSTask or execv
- Resolved
-
JDK-8167711 Change JavawsLauncher.app to use NSTask or execv
- Resolved
-
JDK-8168221 Change JavawsLauncher.app to use NSTask or execv
- Resolved
- relates to
-
JDK-8055464 Add a URL scheme handler to reliably launch .jnlp files - java part
- Closed