Insecure default configuration in Progress Software OpenEdge 10.2x and 11.x allows unauthenticated remote attackers to specify arbitrary URLs from which to load and execute malicious Java classes via port 20931.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Openedge | Progress | 10.2a (including) | 10.2a (including) |
| Openedge | Progress | 10.2b (including) | 10.2b (including) |
| Openedge | Progress | 10.2b07 (including) | 10.2b07 (including) |
| Openedge | Progress | 10.2b08 (including) | 10.2b08 (including) |
| Openedge | Progress | 11.0 (including) | 11.0 (including) |
| Openedge | Progress | 11.1 (including) | 11.1 (including) |
| Openedge | Progress | 11.2 (including) | 11.2 (including) |
| Openedge | Progress | 11.3 (including) | 11.3 (including) |
| Openedge | Progress | 11.4 (including) | 11.4 (including) |
| Openedge | Progress | 11.5 (including) | 11.5 (including) |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: