CVE-2015-9245
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsecure 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceProgress Software OpenEdge 10.2x and 11.x contains an insecure default configuration on port 20931 that allows unauthenticated remote attackers to supply arbitrary URLs from which the application will load and execute malicious Java classes, enabling remote code execution without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 10.2a= 10.2b= 10.2b07= 10.2b08= 11.0= 11.1= 11.2= 11.3= 11.4= 11.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenEdge installation and versionLocate OpenEdge installation directories (commonly under /opt Progress or C:\Progress on Windows) and check for version information in license files, installation logs, or version registry entriesAffected if Installed version matches any of: 10.2a, 10.2b, 10.2b07, 10.2b08, 11.0, 11.1, 11.2, 11.3, 11.4, or 11.5
-
Verify port 20931 is exposedScan the local host or perimeter for TCP port 20931 listening (using netstat, nmap, or equivalent port scanning tool)Affected if Port 20931 is open and accepting connections from untrusted networks
-
Confirm remote class loading is enabledExamine OpenEdge configuration files (typically found in the OpenEdge installation directory under etc or cfg subfolders) for settings that enable remote class loading from arbitrary URLs, such as Java servlet or web service configurations that permit loading classes from non-localhost URLsAffected if Remote class loading from arbitrary URLs is permitted in the configuration and port 20931 is accessible
A system is affected if it runs a vulnerable OpenEdge version (10.2a through 11.5) with port 20931 exposed and remote class loading from arbitrary URLs enabled in the configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedRestrict network access to port 20931 via firewall or disable the vulnerable service; modify OpenEdge configuration to disable remote class loading from arbitrary URLs; apply vendor patches if available.
Progress OpenEdge 11.x or latest supported 12.x release (contact Progress for exact fixed version)
- Identify all servers running OpenEdge 10.2x on port 20931
- Block port 20931 at the network firewall for all external/untrusted sources
- If AdminServer is not required externally, disable it or bind to localhost only
- Verify that only trusted internal IP addresses can reach port 20931
- Consult Progress Knowledgebase article for vendor-specific configuration guidance on securing this port
- Consider upgrading to a supported OpenEdge release as this version is end-of-life
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-9245 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data