Security readout for executives and security teams
Plain-English summary
Progress OpenEdge systems with the AdminServer exposed may allow unauthenticated remote attackers to cause Java classes to load from attacker-controlled locations. In business terms, this is a potentially serious remote compromise path if legacy OpenEdge administration services are reachable from untrusted networks.
Executive priority
Treat as high priority for legacy OpenEdge environments, especially internet-facing or partner-accessible systems. The main urgency is reducing unauthenticated administrative service exposure before deeper vendor-specific remediation planning.
Technical view
CVE-2015-9245 describes an insecure default configuration in Progress Software OpenEdge 10.2x and 11.x. The issue involves AdminServer Java RMI class loading on port 20931, allowing unauthenticated remote attackers to specify arbitrary URLs for malicious Java class loading and execution.
Likely exposure
Exposure is most likely where Progress OpenEdge 10.2x or 11.x AdminServer is running with default or vulnerable configuration and port 20931 is reachable from untrusted networks.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVE description itself supports unauthenticated remote attack potential, but exploit prevalence and patch status are not established by the provided evidence.
Researcher notes
The provided CVE data lacks CVSS, CWE, detailed affected CPEs, and explicit patch information. Analysis is therefore centered on the stated vulnerable OpenEdge versions, AdminServer, Java RMI class loading, and port 20931 exposure.
Mitigation direction
- Review Progress guidance for preventing Java RMI class-loader abuse with AdminServer.
- Restrict AdminServer port 20931 to trusted administrative networks only.
- Identify whether OpenEdge 10.2x or 11.x remains in production.
- Apply vendor-supported configuration changes or updates where Progress documents them.
- Retire or isolate unsupported legacy OpenEdge deployments where feasible.
Validation and detection
- Inventory systems running Progress OpenEdge 10.2x or 11.x.
- Check whether AdminServer is enabled on affected systems.
- Verify whether TCP port 20931 is reachable from untrusted networks.
- Review AdminServer configuration against the Progress knowledgebase guidance.
- Confirm compensating network controls are enforced and monitored.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2015-9245 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://knowledgebase.progress.com/articles/Article/How-to-prevent-Java-RMI-class-loader-exploit-with-AdminServerCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.