CWE-578 Variante Borrador

EJB Bad Practices: Use of Class Loader

This vulnerability occurs when an Enterprise JavaBeans (EJB) component directly manipulates the Java class loader, violating the EJB specification's security and portability rules.

Definición

What is CWE-578?

This vulnerability occurs when an Enterprise JavaBeans (EJB) component directly manipulates the Java class loader, violating the EJB specification's security and portability rules.
The EJB specification establishes clear programming boundaries to ensure beans are portable and securely managed across different container implementations. One of these critical rules explicitly forbids beans from performing low-level JVM operations, including creating or accessing class loaders, modifying security managers, or interfering with system streams. These functions are reserved exclusively for the EJB container itself to maintain a consistent and controlled runtime environment. When a bean bypasses these restrictions, it undermines the container's ability to enforce security policies and manage resources effectively. This can lead to serious security issues, such as class loading conflicts, privilege escalation, or instability, and it breaks the portability guarantee, meaning the bean may fail or behave unpredictably when deployed to a different EJB-compliant application server.
Impacto en el mundo real

Real-world CVEs caused by CWE-578

Todavía no hay CVEs públicos enlazados a esta CWE en el catálogo de MITRE.

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

  1. 1

    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.

  2. 2

    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.

  3. 3

    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.

Ejemplo de código vulnerable

Vulnerable Java

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.

Vulnerable Java 
@Stateless
  public 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) {...}}
Ejemplo de código seguro

Secure pseudo

Seguro 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.
Lista de prevención

How to prevent CWE-578

  • Architecture and Design / Implementation Do not use the Class Loader when writing EJBs.
Señales de detección

How to detect CWE-578

SAST High

Ejecuta análisis estático (SAST) sobre el código buscando el patrón inseguro en el flujo de datos.

DAST Moderate

Ejecuta pruebas dinámicas de seguridad de aplicaciones (DAST) contra el endpoint en vivo.

Runtime Moderate

Vigila los logs en tiempo de ejecución para detectar trazas de excepción inusuales, entradas malformadas o intentos de bypass de autorización.

Code review Moderate

Revisión de código: marca cualquier código nuevo que maneje entrada desde esta superficie sin usar los helpers validados del framework.

Auto-corrección de Plexicus

Plexicus detecta automáticamente CWE-578 y abre un PR de corrección en menos de 60 segundos.

Codex Remedium escanea cada commit, identifica esta debilidad concreta y entrega un pull request listo para revisión con el parche. Sin tickets. Sin traspasos.

Solicitar demo Probar Plexicus gratis
Preguntas frecuentes

Frequently asked questions

¿Qué es CWE-578?

This vulnerability occurs when an Enterprise JavaBeans (EJB) component directly manipulates the Java class loader, violating the EJB specification's security and portability rules.

¿Qué gravedad tiene CWE-578?

MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.

¿Qué lenguajes o plataformas se ven afectados por CWE-578?

MITRE lists the following affected platforms: Java.

¿Cómo puedo prevenir CWE-578?

Do not use the Class Loader when writing EJBs.

¿Cómo detecta y corrige Plexicus CWE-578?

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-578 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.

¿Dónde puedo aprender más sobre CWE-578?

MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/578.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.

Debilidades relacionadas

Weaknesses related to CWE-578

CWE-573 Padre

Improper Following of Specification by Caller

This weakness occurs when software fails to properly follow the documented rules, protocols, or requirements of an external component it…

CWE-103 Hermano

Struts: Incomplete validate() Method Definition

This vulnerability occurs in a Struts application when a validator form either completely omits a validate() method or includes one but…

CWE-104 Hermano

Struts: Form Bean Does Not Extend Validation Class

This vulnerability occurs in Apache Struts applications when a form bean class does not properly extend the framework's validation class.…

CWE-243 Hermano

Creation of chroot Jail Without Changing Working Directory

This vulnerability occurs when a program creates a chroot jail but fails to change its current working directory afterward. Because the…

CWE-253 Hermano

Incorrect Check of Function Return Value

This vulnerability occurs when a program misinterprets or improperly validates the return value from a function, causing it to miss…

CWE-296 Hermano

Improper Following of a Certificate's Chain of Trust

This vulnerability occurs when software fails to properly validate the entire certificate chain back to a trusted root authority. This…

CWE-304 Hermano

Missing Critical Step in Authentication

This vulnerability occurs when a software authentication process omits a required step, weakening its overall security.

CWE-325 Hermano

Missing Cryptographic Step

This vulnerability occurs when a software implementation skips a critical step in a cryptographic process, resulting in security that is…

CWE-329 Hermano

Generation of Predictable IV with CBC Mode

This vulnerability occurs when software uses a predictable or reused Initialization Vector (IV) with Cipher Block Chaining (CBC) mode…

Recursos

Further reading

Listo cuando tú lo estés

Deja de pagar por desarrollador.
Empieza a cerrar el bucle.

Plexicus es el ASPM nativo de IA que escanea, filtra, corrige, pentestea y explica — de forma autónoma. Desarrolladores ilimitados, repos ilimitados, acciones de IA de uso justo. Nivel gratuito real, €269/mo anual cuando estés listo.

Comenzar gratis Reservar una demo