CWE-9 Variant Draft

J2EE Misconfiguration: Weak Access Permissions for EJB Methods

This vulnerability occurs when Enterprise JavaBean (EJB) methods are configured with overly permissive access rights, allowing attackers to exploit elevated privileges they should not have.

Definition

What is CWE-9?

This vulnerability occurs when Enterprise JavaBean (EJB) methods are configured with overly permissive access rights, allowing attackers to exploit elevated privileges they should not have.
A primary indicator of this misconfiguration is the use of the special 'ANYONE' role in the EJB deployment descriptor. Granting this role to methods suggests either incomplete security planning or an application architecture that makes proper access control difficult to implement. This creates a significant risk because it bypasses standard role-based authorization. Attackers can directly invoke sensitive business logic or access data without proper authentication, potentially leading to data breaches, privilege escalation, or unauthorized transactions within the application.
Real-world impact

Real-world CVEs caused by CWE-9

No public CVE references are linked to this CWE in MITRE's catalog yet.

How attackers exploit it

Step-by-step attacker path

  1. 1

    Identify a code path that handles untrusted input without validation.

  2. 2

    Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.

  3. 3

    Deliver the payload through a normal request and observe the application's reaction.

  4. 4

    Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable XML

The following deployment descriptor grants ANYONE permission to invoke the Employee EJB's method named getSalary().

Vulnerable XML 
<ejb-jar>
  	...
  	<assembly-descriptor>
  		<method-permission>
  			<role-name>ANYONE</role-name>
  			<method>
  			<ejb-name>Employee</ejb-name>
  			<method-name>getSalary</method-name>
  		</method-permission>
  	</assembly-descriptor>
  	...
  </ejb-jar>
Secure code example

Secure pseudo

Secure pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist

How to prevent CWE-9

  • Architecture and Design / System Configuration Follow the principle of least privilege when assigning access rights to EJB methods. Permission to invoke EJB methods should not be granted to the ANYONE role.
Detection signals

How to detect CWE-9

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

Plexicus auto-fix

Plexicus auto-detects CWE-9 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-9?

This vulnerability occurs when Enterprise JavaBean (EJB) methods are configured with overly permissive access rights, allowing attackers to exploit elevated privileges they should not have.

How serious is CWE-9?

MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.

What languages or platforms are affected by CWE-9?

MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.

How can I prevent CWE-9?

Follow the principle of least privilege when assigning access rights to EJB methods. Permission to invoke EJB methods should not be granted to the ANYONE role.

How does Plexicus detect and fix CWE-9?

Plexicus's SAST engine matches the data-flow signature for CWE-9 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-9?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/9.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-9

CWE-266 Parent

Incorrect Privilege Assignment

This vulnerability occurs when a system mistakenly grants a user, process, or entity a specific permission or privilege they should not…

CWE-1022 Sibling

Use of Web Link to Untrusted Target with window.opener Access

This vulnerability occurs when a web application links to an external, untrusted site without protecting its own window from being…

CWE-520 Sibling

.NET Misconfiguration: Use of Impersonation

This vulnerability occurs when a .NET application is configured to run with impersonation, potentially granting it excessive system-level…

CWE-556 Sibling

ASP.NET Misconfiguration: Use of Identity Impersonation

This vulnerability occurs when an ASP.NET application is configured to run using impersonated credentials, which can grant the application…

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.

Get started free Book a demo