public class WrapperPermission
extends java.security.BasicPermission
| Permission Target Name | What the Permission Allows | Risks of Allowing this Permission |
|---|---|---|
| getInteractiveUser | Obtain the user who is currently logged on and whose desktop the Wrapper is interacting with. | This discloses the account name and, when groups are requested, the groups of the interactive user. Malicious code could use this information to find other weaknesses in the system. |
| getJavaPID | Obtain the PID of the Java process. | This discloses a process identifier. Malicious code could use it to target the JVM from outside the process. |
| getProperties | Obtain the expanded contents of the Wrapper configuration file. | This discloses the configuration used to launch the Wrapper. Properties that can contain sensitive data are excluded by default, but the remaining configuration can still reveal how the system is set up. |
| getUser | Obtain the user under which the Wrapper is currently running. | This discloses the account name and, when groups are requested, the groups of the Wrapper user. Malicious code could use this information to find other weaknesses in the system. |
| getWrapperPID | Obtain the PID of the Wrapper process. | This discloses a process identifier. Malicious code could use it to target the Wrapper from outside the process. |
| listServices | Requests the status of all services currently installed on the system. | Malicious code could use this information to find other weaknesses in the system. |
| log | Sends log output to the Wrapper over the back end socket at a specific log level. | Malicious code could send very large quanities of log output which could affect the performance of the Wrapper. |
| removeWrapperEventListener | Stop a previously registered listener from receiving Wrapper events. | Malicious code could remove a listener that the application relies on to notice shutdown, logoff, or other control events. |
| requestThreadDump | Request a thread dump of the current JVM. | A thread dump can disclose application state, including class and method names. Requesting dumps repeatedly can also affect the performance of the JVM. |
| restart | Restart the JVM | This is an extremely dangerous permission to grant. Malicious applications can restart the JVM as a denial of service attack. |
| resumeTimeouts | Resume Wrapper timeouts that were previously suspended. | Malicious code could resume timeouts while the application is still blocked, causing the Wrapper to treat the JVM as unresponsive. |
| setConsoleTitle | Set the title of the console in which the Wrapper is running. | Malicious code could change the console title and mislead a user about which application is running. |
| signalStarting | Control the starting timeouts. | Malicious code could set this to unrealistically small values as the application is starting, thus causing startup failures. |
| signalStopped | Control when the Wrapper is told that the Application has stopped. | Malicious code could call this before the application is actually stopped, thus causing the application to fail to shutdown cleanly. |
| signalStopping | Control the stopping timeouts. | Malicious code could set this to unrealistically small values as the application is stopping, thus causing the application to fail to shutdown cleanly. |
| stop | Stop the JVM | This is an extremely dangerous permission to grant. Malicious applications can stop the JVM as a denial of service attack. |
| stopImmediate | Stop the JVM immediately without running the shutdown hooks | This is an extremely dangerous permission to grant. Malicious applications can stop the JVM as a denial of service attack. |
| suspendTimeouts | Suspend the timeouts used by the Wrapper to monitor the JVM. | Malicious code could suspend timeouts so that a hung JVM is not detected and restarted. |
| test.accessViolationNative | Cause an access violation within native JNI code. This is a testing method. | This is an extremely dangerous permission to grant. It is expected to crash the JVM. |
| test.appearHung | Make the JVM appear hung when viewed from the native Wrapper. This is a testing method. | Malicious code could make a healthy JVM appear hung, causing the Wrapper to restart or stop it. |
| test.appearSlow | Delay responses to the Wrapper so the JVM appears sluggish. This is a testing method. | Malicious code could delay responses long enough for the Wrapper to treat the JVM as unresponsive. |
| test.raiseExceptionNative | Raise an exception in native code. This is a testing method. | This is an extremely dangerous permission to grant. It is expected to crash the JVM. |
| test.raiseFailFastExceptionNative | Raise a fail fast exception in native code. This is a testing method. | This is an extremely dangerous permission to grant. It is expected to terminate the JVM immediately. |
| Constructor and Description |
|---|
WrapperPermission(java.lang.String name)
Creates a new WrapperPermission with the specified name.
|
WrapperPermission(java.lang.String name,
java.lang.String actions)
Creates a new WrapperPermission with the specified name.
|
public WrapperPermission(java.lang.String name)
name - the name of the WrapperPermission.public WrapperPermission(java.lang.String name,
java.lang.String actions)
name - the name of the WrapperPermission.actions - The event type or event types to be registered.Copyright 1999, 2026 Tanuki Software Inc., All Rights Reserved.