VariantDraft

CWE-576EJB Bad Practices: Use of Java I/O

Category: other

Description

The product violates the Enterprise JavaBeans (EJB) specification by using the java.io package. 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: "An enterprise bean must not use the java.io package to attempt to access files and directories in the file system." The specification justifies this requirement in the following way: "The file system APIs are not well-suited for business components to access data. Business components should use a resource manager API, such as JDBC, to store data."

Common consequences· 1

  • Other — Quality Degradation

Potential mitigations· 1

  • [Implementation]Do not use Java I/O when writing EJBs.

References

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

Related by meaning· 6

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

CWE
EJB Bad Practices: Use of Class Loader
CWE
EJB Bad Practices: Use of Sockets
CWE
EJB Bad Practices: Use of AWT Swing
CWE
EJB Bad Practices: Use of Synchronization Primitives
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.