First published: Tue Oct 31 2017(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Progress OpenEdge Explorer | =10.2a | |
Progress OpenEdge Explorer | =10.2b | |
Progress OpenEdge Explorer | =10.2b07 | |
Progress OpenEdge Explorer | =10.2b08 | |
Progress OpenEdge Explorer | =11.0 | |
Progress OpenEdge Explorer | =11.1 | |
Progress OpenEdge Explorer | =11.2 | |
Progress OpenEdge Explorer | =11.3 | |
Progress OpenEdge Explorer | =11.4 | |
Progress OpenEdge Explorer | =11.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-9245 is rated as a high severity vulnerability due to the potential for unauthenticated remote code execution.
To fix CVE-2015-9245, configure the Progress OpenEdge to disable the insecure Java RMI settings and restrict URL class loading.
CVE-2015-9245 affects Progress Software OpenEdge versions 10.2a, 10.2b, and all versions from 11.0 to 11.5.
Yes, CVE-2015-9245 can be exploited remotely by attackers to load and execute malicious Java classes.
Yes, CVE-2015-9245 is related to Java security as it involves the insecure configuration of Java RMI class loading.