CWE-578 Variante Rascunho

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.

Definição

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 no mundo real

Real-world CVEs caused by CWE-578

Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.

Como os atacantes a exploram

Trajeto do atacante passo a passo

  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.

Exemplo de código vulnerável

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.

Vulnerável 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) {...}}
Exemplo 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 verificação de prevenção

How to prevent CWE-578

  • Architecture and Design / Implementation Do not use the Class Loader when writing EJBs.
Sinais de deteção

How to detect CWE-578

SAST High

Executar análise estática (SAST) na base de código à procura do padrão inseguro no fluxo de dados.

DAST Moderate

Executar testes dinâmicos de segurança de aplicações (DAST) contra o endpoint em execução.

Runtime Moderate

Monitorizar os registos em tempo de execução para traços de exceção invulgares, input malformado ou tentativas de contornar a autorização.

Code review Moderate

Revisão de código: sinalizar qualquer novo código que trate input desta superfície sem usar os ajudantes validados do framework.

Correção automática do Plexicus

O Plexicus deteta automaticamente o CWE-578 e abre um PR de correção em menos de 60 segundos.

O Codex Remedium analisa cada commit, identifica esta fraqueza exata e entrega um pull request pronto para revisão com o patch. Sem tickets. Sem transferências.

Obter uma demonstração Experimente o Plexicus gratuitamente
Perguntas frequentes

Frequently asked questions

O que é o 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.

Qual a gravidade do CWE-578?

A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.

Que linguagens ou plataformas são afetadas pelo CWE-578?

MITRE lists the following affected platforms: Java.

Como posso prevenir o CWE-578?

Do not use the Class Loader when writing EJBs.

Como é que o Plexicus deteta e corrige o CWE-578?

O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-578 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.

Onde posso saber mais sobre o CWE-578?

A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/578.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.

Fraquezas relacionadas

Weaknesses related to CWE-578

CWE-573 Pai

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 Irmão

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 Irmão

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 Irmão

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 Irmão

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 Irmão

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 Irmão

Missing Critical Step in Authentication

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

CWE-325 Irmão

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 Irmão

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

Pronto quando você estiver

Pare de pagar por desenvolvedor.
Comece a fechar o ciclo.

O Plexicus é o ASPM nativo de IA que verifica, filtra, corrige, pentesta e explica — de forma autónoma. Programadores ilimitados, repos ilimitados, ações de IA de utilização justa. Nível gratuito real, €269/mo anual quando estiver pronto.

Começar grátis Reservar uma demo