CWE-578: EJB Bad Practices: Use of Class Loader

Extended Description

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."

Code Examples & CVEs

Demonstrative Examples

The following Java example is a simple stateless Enterprise JavaBean that retrieves the interest rate for the number of points for a mortgage. The interest rates for various points are retrieved from an XML document on the local file system, and the EJB uses the Class Loader for the EJB class to obtain the XML document from the local file system as an input stream.

This use of the Java Class Loader class within any kind of Enterprise JavaBean violates the restriction of the EJB specification against obtaining the current class loader as this could compromise the security of the application using the EJB.

BadJava

@Statelesspublic class InterestRateBean implements InterestRateRemote {                                               private Document interestRateXMLDocument = null;                            public InterestRateBean() {                               try {                                                                                                                     // get XML document from the local filesystem as an input stream                                                                                                                        // using the ClassLoader for this class                                        ClassLoader loader = this.getClass().getClassLoader();InputStream in = loader.getResourceAsStream(Constants.INTEREST_RATE_FILE);                                                                                                                                                     DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();DocumentBuilder db = dbf.newDocumentBuilder();interestRateXMLDocument = db.parse(interestRateFile);} catch (IOException ex) {...}                      }                                               public BigDecimal getInterestRate(Integer points) {return getInterestRateFromXML(points);}                                                        /* member function to retrieve interest rate from XML document on the local file system */                                                        private BigDecimal getInterestRateFromXML(Integer points) {...}                      }

An EJB is also restricted from creating a custom class loader and creating a class and instance of a class from the class loader, as shown in the following example.

BadJava

@Statelesspublic class LoaderSessionBean implements LoaderSessionRemote {                                               public LoaderSessionBean() {try {ClassLoader loader = new CustomClassLoader();Class c = loader.loadClass("someClass");Object obj = c.newInstance();/* perform some task that uses the new class instance member variables or functions */...} catch (Exception ex) {...}}                            public class CustomClassLoader extends ClassLoader {                            }                      }

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-578 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-578, EJB Bad Practices: Use of Class Loader, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address EJB Bad Practices: Use of Class Loader during Architecture and Design

MITRE associates mitigation with Architecture and Design, and Implementation; recorded impacts include Execute Unauthorized Code or Commands, and Varies by Context; related weaknesses include CWE-573. Use these source-defined anchors to turn CWE-578 into implementation, review, and verification checks for the affected component.

CWE-578: EJB Bad Practices: Use of Class Loader — MITRE CWE

Triage CWE-578 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-578, EJB Bad Practices: Use of Class Loader, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-578

Apply MITRE's full root-cause mapping guidance when using CWE-578, EJB Bad Practices: Use of Class Loader. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-578 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-578, EJB Bad Practices: Use of Class Loader. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-578: EJB Bad Practices: Use of Class Loader?+

CWE-578: EJB Bad Practices: Use of Class Loader is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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."

What are the security consequences of EJB Bad Practices: Use of Class Loader?+

If exploited, CWE-578 (EJB Bad Practices: Use of Class Loader) it can compromise Confidentiality, Integrity, Availability and Other, leading to outcomes such as Execute Unauthorized Code or Commands and Varies by Context.

How do you prevent or mitigate EJB Bad Practices: Use of Class Loader?+

Recommended mitigations for CWE-578 include: Do not use the Class Loader when writing EJBs.

Which programming languages are affected by EJB Bad Practices: Use of Class Loader?+

CWE-578 commonly affects Java. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-578 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-578: EJB Bad Practices: Use of Class Loader

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods