CVE-2020-13951 — openmeetings-parent
HIGHCVE-2020-13951 is a high-severity (CVSS 7.5) vulnerability in org.apache.openmeetings:openmeetings-parent. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.apache.openmeetings:openmeetings-parent — see the affected versions and patch details below.
Denial of service in Apache OpenMeetings
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-13951 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.apache.openmeetings:openmeetings-parentReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Attackers can use public NetTest web service of Apache OpenMeetings 4.0.0-5.0.0 to organize denial of service attack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.openmeetings:openmeetings-parent | ≥ 4.0.0&&< 5.1.0 | 5.1.0org.apache.openmeetings:openmeetings-parent:5.1.0 |
Affected Products
openmeetingsapacheResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Apache OpenMeetings 5.0.0 - 'hostname' Denial of Service
by SunCSR · Nov 24, 2020
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.openmeetings:openmeetings-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.openmeetings:openmeetings-parent to 5.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-13951 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2020-13951 in your dependencies?
Find it across Maven, including transitive dependencies.