Page History

...

This guideline addresses the problem of excess privileges. See 17. SEC50-JG. Avoid granting excess privileges for another approach to solving this problem.

...

By default, permissions cannot be defined to support actions using BasicPermission, but the actions can be freely implemented in the subclass ExceptionReporterPermission if required. BasicPermission is abstract even though it contains no abstract methods; it defines all the methods that it extends from the Permission class. The custom-defined subclass of the BasicPermission class has to define two constructors to call the most appropriate (one- or two-argument) superclass constructor (the superclass lacks a default constructor). The two-argument constructor also accepts an action even though a basic permission does not use it. This behavior is required for constructing permission objects from the policy file. Note that the custom-defined subclass of the BasicPermission class is declared to be final in accordance with guideline 15. OBJ56-JG. Classes that derive from a sensitive class or implement a sensitive interface must be declared Either design classes for inheritance or declare them as final.

Applicability

Running Java code without defining custom permissions where default permissions are inapplicable can leave an application open to privilege escalation vulnerabilities.

Related Guidelines

...

Bibliography

...