CVE-2016-8736: Critical severity apache openmeetings vulnerability

Published Oct 12, 2017
·
Updated

Apache OpenMeetings before 3.1.2 is vulnerable to Remote Code Execution via RMI deserialization attack.

Affected Software

2 affected componentsFixes available
Apache OpenMeetings<3.1.2
maven/org.apache.openmeetings:openmeetings-parent<3.1.2
3.1.2

Event History

Oct 12, 2017
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
May 14, 2022
Advisory Published
01:29 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2016-8736?

CVE-2016-8736 is rated as critical due to its potential for remote code execution.

2

How do I fix CVE-2016-8736?

To fix CVE-2016-8736, upgrade Apache OpenMeetings to version 3.1.2 or later.

3

What type of attack does CVE-2016-8736 involve?

CVE-2016-8736 involves a Remote Code Execution attack via RMI deserialization.

4

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.

5

Is it possible to exploit CVE-2016-8736 remotely?

Yes, CVE-2016-8736 can be exploited remotely, enabling unauthorized code execution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203