Programs must comply with the principle of least privilege not only by providing privileged blocks with the minimum permissions required for correct operation (see 171. SEC50-JG16. Avoid granting excess privileges) but also by ensuring that privileged code contains only those operations that require the increased privileges. Superfluous code contained within a privileged block necessarily operates with the privileges of that block, increasing the attack surface.
Noncompliant Code Example
This noncompliant code example contains a changePassword() method that attempts to open a password file within a doPrivileged block and performs operations using that file. The doPrivileged block also contains a superfluous System.loadLibrary() call that loads the authentication library.
...
This example violates the principle of least privilege because an unprivileged caller will also cause the authentication library to be loaded. An unprivileged caller should not be allowed to invoke the System.loadLibrary() method, especially via the doPrivileged mechanism, because System.loadLibrary uses only the immediate caller's class loader to find and load the library. Unprivileged code is seldom granted privileges to load libraries because doing so would expose native methods to the unprivileged code [SCG 2010].
Compliant Solution
This compliant solution moves the call to System.loadLibrary() outside the doPrivileged() block. Doing so allows unprivileged code to perform preliminary password-reset checks using the file but prevents it from loading the authentication library.
...
The loadLibrary() invocation could also occur before preliminary password-reset checks are performed; in this case, it is deferred for performance reasons.
Applicability
Minimizing privileged code reduces the attack surface of an application and simplifies the task of auditing privileged code.
Bibliography
...