Executar análise estática (SAST) na base de código à procura do padrão inseguro no fluxo de dados.
CWE-576 Variante Rascunho
EJB Bad Practices: Use of Java I/O
This vulnerability occurs when an Enterprise JavaBeans (EJB) component incorrectly uses Java I/O (java.io) operations to access the file system, violating the EJB specification's design principles.
Definição
What is CWE-576?
This vulnerability occurs when an Enterprise JavaBeans (EJB) component incorrectly uses Java I/O (java.io) operations to access the file system, violating the EJB specification's design principles.
The EJB specification explicitly prohibits the use of java.io package file system access within enterprise beans. This restriction exists because EJB components are designed as portable business logic units that should remain independent of the server's underlying file structure. Using standard file I/O ties your component to a specific server environment, breaking portability and creating inconsistent behavior across different EJB containers.
Instead of file system access, EJB components should interact with data through managed resource APIs like JDBC for databases or JMS for messaging. These standardized interfaces ensure proper transaction management, security, and scalability within the container's managed environment. Following this practice maintains the component's portability and leverages the container's built-in services for reliable data handling.
Impacto no mundo real
Real-world CVEs caused by CWE-576
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
The following Java example is a simple stateless Enterprise JavaBean that retrieves the interest rate for the number of points for a mortgage. In this example, the interest rates for various points are retrieved from an XML document on the local file system, and the EJB uses the Java I/O API to retrieve the XML document from the local file system.
- 2
This use of the Java I/O API within any kind of Enterprise JavaBean violates the EJB specification by using the java.io package for accessing files within the local filesystem.
- 3
An Enterprise JavaBean should use a resource manager API for storing and accessing data. In the following example, the private member function getInterestRateFromXMLParser uses an XML parser API to retrieve the interest rates.
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. In this example, the interest rates for various points are retrieved from an XML document on the local file system, and the EJB uses the Java I/O API to retrieve the XML document from the local file system.
@Stateless
public class InterestRateBean implements InterestRateRemote {
private Document interestRateXMLDocument = null;
private File interestRateFile = null;
public InterestRateBean() {
try {
```
/* get XML document from the local filesystem */*
interestRateFile = new File(Constants.INTEREST_RATE_FILE);
if (interestRateFile.exists())
{
```
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 Java
An Enterprise JavaBean should use a resource manager API for storing and accessing data. In the following example, the private member function getInterestRateFromXMLParser uses an XML parser API to retrieve the interest rates.
@Stateless
public class InterestRateBean implements InterestRateRemote {
public InterestRateBean() {
}
public BigDecimal getInterestRate(Integer points) {
return getInterestRateFromXMLParser(points);
}
```
/* member function to retrieve interest rate from XML document using an XML parser API */*
private BigDecimal getInterestRateFromXMLParser(Integer points) {...}} 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-576
- Implementation Do not use Java I/O when writing EJBs.
Sinais de deteção
How to detect CWE-576
Executar testes dinâmicos de segurança de aplicações (DAST) contra o endpoint em execução.
Monitorizar os registos em tempo de execução para traços de exceção invulgares, input malformado ou tentativas de contornar a autorização.
Revisão de código: sinalizar qualquer novo código que trate input desta superfície sem usar os ajudantes validados do framework.
CWE-576
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Perguntas frequentes O que é o CWE-576?
Qual a gravidade do CWE-576?
Que linguagens ou plataformas são afetadas pelo CWE-576?
Como posso prevenir o CWE-576?
Como é que o Plexicus deteta e corrige o CWE-576?
Onde posso saber mais sobre o CWE-576?
Frequently asked questions
O que é o CWE-576?
This vulnerability occurs when an Enterprise JavaBeans (EJB) component incorrectly uses Java I/O (java.io) operations to access the file system, violating the EJB specification's design principles.
Qual a gravidade do CWE-576?
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-576?
MITRE lists the following affected platforms: Java.
Como posso prevenir o CWE-576?
Do not use Java I/O when writing EJBs.
Como é que o Plexicus deteta e corrige o CWE-576?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-576 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-576?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/576.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-576
CWE-695 Pai
Use of Low-Level Functionality
This vulnerability occurs when code bypasses high-level framework controls by directly using low-level system functions, violating the…
CWE-111 Irmão
Direct Use of Unsafe JNI
This weakness occurs when a Java application directly calls native code through the Java Native Interface (JNI), exposing the entire…
CWE-245 Irmão
J2EE Bad Practices: Direct Management of Connections
This vulnerability occurs when a J2EE application handles database connections directly instead of using the container's built-in…
CWE-246 Irmão
J2EE Bad Practices: Direct Use of Sockets
This vulnerability occurs when a J2EE application creates network sockets directly, bypassing the container-managed communication…
CWE-383 Irmão
J2EE Bad Practices: Direct Use of Threads
Creating or managing threads directly within a J2EE application is a risky practice that violates the platform's standards and often leads…
CWE-574 Irmão
EJB Bad Practices: Use of Synchronization Primitives
This vulnerability occurs when an Enterprise JavaBeans (EJB) component improperly uses thread synchronization primitives, violating the…
CWE-575 Irmão
EJB Bad Practices: Use of AWT Swing
This vulnerability occurs when an Enterprise JavaBeans (EJB) component incorrectly uses AWT or Swing UI toolkits, violating the EJB…
Pronto para validar o que importa?
Pronto para validar o que importa.
O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.