CWE-574: EJB Bad Practices: Use of Synchronization Primitives
The product violates the Enterprise JavaBeans (EJB) specification by using thread synchronization primitives.
How it's found
EJB Bad Practices: Use of Synchronization Primitives is a specific, narrowly defined instance of a broader pattern. Testers confirm it with targeted code review and a proof-of-concept input that exercises the exact code path this weakness describes.
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 thread synchronization primitives to synchronize execution of multiple instances." The specification justifies this requirement in the following way: "This rule is required to ensure consistent runtime semantics because while some EJB containers may use a single JVM to execute all enterprise bean's instances, others may distribute the instances across multiple JVMs."
Consequences
- Quality Degradation
Mitigations
- Implementation: Do not use Synchronization Primitives when writing EJBs.
Where this fits in a TurboPentest engagement
TurboPentest's agentic pentest is powerful and covers a broad range of issues automatically. This particular class is best confirmed in a manual IntegSec engagement, where human pentesters apply deeper methodology and a larger context window than any automated pass.
Frequently asked questions
What is CWE-574?
The product violates the Enterprise JavaBeans (EJB) specification by using thread synchronization primitives.
How do you find EJB Bad Practices: Use of Synchronization Primitives?
EJB Bad Practices: Use of Synchronization Primitives is a specific, narrowly defined instance of a broader pattern. Testers confirm it with targeted code review and a proof-of-concept input that exercises the exact code path this weakness describes.
What is the impact of CWE-574?
Quality Degradation
Does TurboPentest test for EJB Bad Practices: Use of Synchronization Primitives?
TurboPentest's agentic pentest is powerful and covers a broad range of issues automatically. This particular class is best confirmed in a manual IntegSec engagement, where human pentesters apply deeper methodology and a larger context window than any automated pass.
Related CWEs
Find these issues before an attacker does
TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.
Start a $99 pentest