70 matches found
CVE-2008-2078
Robocode before 1.6.0 allows user-assisted remote attackers to "access the internals of the Robocode game" via unspecified vectors related to the AWT Event Queue...
CVE-2008-2078
Robocode before 1.6.0 allows user-assisted remote attackers to "access the internals of the Robocode game" via unspecified vectors related to the AWT Event Queue...
CVE-2008-2078
CVE-2008-2078 affects Robocode prior to 1.6.0. The vulnerability allows user‑assisted remote attackers to access the internals of the Robocode game via vectors related to the AWT Event Queue. Root cause and affected component: Robocode before 1.6.0, with the issue tied to the AWT Event Queue hand...
CVE-2008-2078
Robocode before 1.6.0 allows user-assisted remote attackers to "access the internals of the Robocode game" via unspecified vectors related to the AWT Event Queue...
CVE-2008-2078
Robocode before 1.6.0 allows user-assisted remote attackers to "access the internals of the Robocode game" via unspecified vectors related to the AWT Event Queue...
Design/Logic Flaw
The Event Dispatch Thread in Robocode before 1.5.1 allows remote attackers to execute arbitrary Java code by using a robot to invoke the SwingUtilities.invokeLater method...
CVE-2007-6382
The Event Dispatch Thread in Robocode before 1.5.1 allows remote attackers to execute arbitrary Java code by using a robot to invoke the SwingUtilities.invokeLater method...
CVE-2007-6382
Summary: Robocode versions before 1.5.1 are affected by an arbitrary code execution vulnerability involving the Event Dispatch Thread (EDT). According to the documents, a robot can trigger Java code execution by invoking SwingUtilities.invokeLater on the EDT. Affected product/component: Robocode ...
CVE-2007-6382
The Event Dispatch Thread in Robocode before 1.5.1 allows remote attackers to execute arbitrary Java code by using a robot to invoke the SwingUtilities.invokeLater method...
CVE-2007-6382
The Event Dispatch Thread in Robocode before 1.5.1 allows remote attackers to execute arbitrary Java code by using a robot to invoke the SwingUtilities.invokeLater method...