CVE-2016-8736
First published: Thu Oct 12 2017(Updated: )
Apache OpenMeetings before 3.1.2 is vulnerable to Remote Code Execution via RMI deserialization attack.
Credit: security@apache.org security@apache.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Apache OpenMeetings | <3.1.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-8736?
CVE-2016-8736 is rated as critical due to its potential for remote code execution.
How do I fix CVE-2016-8736?
To fix CVE-2016-8736, upgrade Apache OpenMeetings to version 3.1.2 or later.
What type of attack does CVE-2016-8736 involve?
CVE-2016-8736 involves a Remote Code Execution attack via RMI deserialization.
Which versions of Apache OpenMeetings are affected by CVE-2016-8736?
Apache OpenMeetings versions prior to 3.1.2 are affected by CVE-2016-8736.
Is it possible to exploit CVE-2016-8736 remotely?
Yes, CVE-2016-8736 can be exploited remotely, enabling unauthorized code execution.
- collector/nvd-index
- collector/github-advisory-latest
- alias/GHSA-6cpg-3w7f-j67q
- alias/CVE-2016-8736
- collector/nvd-cve
- collector/github-advisory
- agent/author
- agent/type
- agent/references
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- agent/trending
- agent/tags
- agent/source
- vendor/apache
- canonical/apache openmeetings
- package-manager/maven