nerdexam
Oracle

1Z0-819 · Question #58

You are working on a functional bug in a tool used by your development organization. In your investigation, you find that the tool is executed with a security policy file containing this grant…

The correct answer is D. Flag a security bug against the tool ref factoring the excessive permission granted. D is correct because discovering AllPermission in a security policy - even during unrelated bug investigation - represents a security vulnerability that must be reported. The principle of least privilege dictates that code should only have the specific permissions it needs…

Secure Coding in Java SE

Question

You are working on a functional bug in a tool used by your development organization. In your investigation, you find that the tool is executed with a security policy file containing this grant. grant codebase "file:${klib.home}/j2se/home/klib.jar" { permission java.security.AllPermission; }; What action should you take?

Options

  • ANothing, because it is an internal tool and not exposed to the public.
  • BNothing, because bugs are to be expected.
  • CNothing, because it is not related to the bug you are investigating.
  • DFlag a security bug against the tool ref factoring the excessive permission granted.
  • ENothing, because adding all the required permissions would be an ongoing maintenance challenge.

How the community answered

(44 responses)
  • A
    2% (1)
  • B
    5% (2)
  • C
    9% (4)
  • D
    84% (37)

Explanation

D is correct because discovering AllPermission in a security policy - even during unrelated bug investigation - represents a security vulnerability that must be reported. The principle of least privilege dictates that code should only have the specific permissions it needs; granting AllPermission removes all sandbox protections and exposes the JVM to privilege escalation, file system access, network access, and more.

Why the distractors fail:

  • A is wrong because internal tools are still attack surfaces - insider threats, compromised dependencies, and lateral movement all exploit internal systems.
  • B is wrong because security misconfigurations are not acceptable technical debt; they carry real risk regardless of other bugs.
  • C is wrong because responsible security practice requires reporting findings even when out of scope for your current task - you have a duty to flag it.
  • E is wrong because maintenance burden does not justify granting unlimited permissions; the correct approach is to enumerate only necessary permissions, not avoid the work entirely.

Memory tip: Think of AllPermission as giving someone a master key to your entire building just because they needed to access one room. Whenever you see it in a policy file, it's almost always a flag - the fix is to replace it with the specific, minimal permissions actually required.

Topics

#Java security policies#AllPermission grant#Secure coding practices#Permission management

Community Discussion

No community discussion yet for this question.

Full 1Z0-819 Practice