Führe statische Analyse (SAST) auf der Codebasis aus und suche im Datenfluss nach dem unsicheren Muster.
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 specification's design principles.
What is CWE-575?
Real-world CVEs caused by CWE-575
Bisher sind in MITREs Katalog keine öffentlichen CVE-Referenzen mit dieser CWE verknüpft.
Angreiferpfad Schritt für Schritt
- 1
The following Java example is a simple converter class for converting US dollars to Yen. This converter class demonstrates the improper practice of using a stateless session Enterprise JavaBean that implements an AWT Component and AWT keyboard event listener to retrieve keyboard input from the user for the amount of the US dollars to convert to Yen.
- 2
This use of the AWT and Swing APIs within any kind of Enterprise JavaBean not only violates the restriction of the EJB specification against using AWT or Swing within an EJB but also violates the intended use of Enterprise JavaBeans to separate business logic from presentation logic.
- 3
The Stateless Session Enterprise JavaBean should contain only business logic. Presentation logic should be provided by some other mechanism such as Servlets or Java Server Pages (JSP) as in the following Java/JSP example.
Vulnerable Java
The following Java example is a simple converter class for converting US dollars to Yen. This converter class demonstrates the improper practice of using a stateless session Enterprise JavaBean that implements an AWT Component and AWT keyboard event listener to retrieve keyboard input from the user for the amount of the US dollars to convert to Yen.
@Stateless
public class ConverterSessionBean extends Component implements KeyListener, ConverterSessionRemote {
```
/* member variables for receiving keyboard input using AWT API */*
...
private StringBuffer enteredText = new StringBuffer();
*/* conversion rate on US dollars to Yen */*
private BigDecimal yenRate = new BigDecimal("115.3100");
public ConverterSessionBean() {
```
super();
```
/* method calls for setting up AWT Component for receiving keyboard input */*
...
addKeyListener(this);}
public BigDecimal dollarToYen(BigDecimal dollars) {
```
BigDecimal result = dollars.multiply(yenRate);
return result.setScale(2, BigDecimal.ROUND_DOWN);
}
```
/* member functions for implementing AWT KeyListener interface */*
public void keyTyped(KeyEvent event) {
```
...
}
public void keyPressed(KeyEvent e) {
}
public void keyReleased(KeyEvent e) {
}
```
/* member functions for receiving keyboard input and displaying output */*
public void paint(Graphics g) {...}
...} Secure Java
The Stateless Session Enterprise JavaBean should contain only business logic. Presentation logic should be provided by some other mechanism such as Servlets or Java Server Pages (JSP) as in the following Java/JSP example.
@Stateless
public class ConverterSessionBean implements ConverterSessionRemoteInterface {
```
/* conversion rate on US dollars to Yen */*
private BigDecimal yenRate = new BigDecimal("115.3100");
public ConverterSessionBean() {
}
*/* remote method to convert US dollars to Yen */*
public BigDecimal dollarToYen(BigDecimal dollars) {
```
BigDecimal result = dollars.multiply(yenRate);
return result.setScale(2, BigDecimal.ROUND_DOWN);
}
} How to prevent CWE-575
- Architecture and Design Do not use AWT/Swing when writing EJBs.
How to detect CWE-575
Führe dynamische Application-Security-Tests gegen den Live-Endpoint aus.
Beobachte Runtime-Logs auf ungewöhnliche Exception-Traces, fehlerhafte Eingaben oder Versuche, Autorisierung zu umgehen.
Code Review: Markiere jeden neuen Code, der Eingaben von dieser Oberfläche ohne validierte Framework-Helper verarbeitet.
Plexicus erkennt CWE-575 automatisch und öffnet in unter 60 Sekunden einen Fix-PR.
Codex Remedium scannt jeden Commit, identifiziert genau diese Schwachstelle und liefert einen reviewer-ready Pull Request mit dem Patch. Keine Tickets. Keine Hand-offs.
Frequently asked questions
Was ist CWE-575?
This vulnerability occurs when an Enterprise JavaBeans (EJB) component incorrectly uses AWT or Swing UI toolkits, violating the EJB specification's design principles.
Wie gravierend ist CWE-575?
MITRE hat für diese Schwachstelle keine Exploit-Wahrscheinlichkeit veröffentlicht. Behandle sie als mittlere Auswirkung, bis dein Threat Model anderes belegt.
Welche Sprachen oder Plattformen sind von CWE-575 betroffen?
MITRE lists the following affected platforms: Java.
Wie kann ich CWE-575 verhindern?
Do not use AWT/Swing when writing EJBs.
Wie erkennt und behebt Plexicus CWE-575?
Die SAST-Engine von Plexicus erkennt die Datenfluss-Signatur von CWE-575 bei jedem Commit. Bei einem Treffer öffnet unser Codex-Remedium-Agent einen Fix-PR mit korrigiertem Code, Tests und einer einzeiligen Zusammenfassung für den Reviewer.
Wo erfahre ich mehr über CWE-575?
MITRE veröffentlicht die kanonische Definition unter https://cwe.mitre.org/data/definitions/575.html. Für ergänzende Hinweise kannst du auch die OWASP- und NIST-Dokumentation heranziehen.
Weaknesses related to CWE-575
Use of Low-Level Functionality
This vulnerability occurs when code bypasses high-level framework controls by directly using low-level system functions, violating the…
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…
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…
J2EE Bad Practices: Direct Use of Sockets
This vulnerability occurs when a J2EE application creates network sockets directly, bypassing the container-managed communication…
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…
EJB Bad Practices: Use of Synchronization Primitives
This vulnerability occurs when an Enterprise JavaBeans (EJB) component improperly uses thread synchronization primitives, violating the…
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…
Further reading
Schluss mit dem Bezahlen pro Entwickler.
Schließ den Kreislauf.
Plexicus ist die KI-native ASPM, die scannt, filtert, fixt, pentestet und erklärt — autonom. Unbegrenzte Entwickler, unbegrenzte Repos, Fair-Use-KI-Aktionen. Echter kostenloser Tarif, €269/mo jährlich, wenn du bereit bist.