VariantDraft

CWE-578EJB Bad Practices: Use of Class Loader

Category: other

Description

The product violates the Enterprise JavaBeans (EJB) specification by using the class loader. The Enterprise JavaBeans specification requires that every bean provider follow a set of programming guidelines designed to ensure that the bean will be portable and behave consistently in any EJB container. In this case, the product violates the following EJB guideline: "The enterprise bean must not attempt to create a class loader; obtain the current class loader; set the context class loader; set security manager; create a new security manager; stop the JVM; or change the input, output, and error streams." The specification justifies this requirement in the following way: "These functions are reserved for the EJB container. Allowing the enterprise bean to use these functions could compromise security and decrease the container's ability to properly manage the runtime environment."

Common consequences· 1

  • Confidentiality / Integrity / Availability / Other — Execute Unauthorized Code or Commands, Varies by Context

Potential mitigations· 1

  • [Architecture and Design, Implementation]Do not use the Class Loader when writing EJBs.

References

  1. https://cwe.mitre.org/data/definitions/578.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
EJB Bad Practices: Use of Sockets
CWE
EJB Bad Practices: Use of Synchronization Primitives
CWE
EJB Bad Practices: Use of Java I/O
CWE
EJB Bad Practices: Use of AWT Swing
CWE
J2EE Bad Practices: Non-serializable Object Stored in Session
CWE
Runtime Resource Management Control Element in a Component Built to Run on Application Servers
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.