CVE-2017-7688

Apache OpenMeetings version 1.0.0 does not check the contents of uploaded files. An attacker can cause a denial of service by uploading multiple large files to the server.

Apache OpenMeetings version 1.0.0 discloses Tomcat version and detailed error stack trace, which is not secure.

Apache OpenMeetings version 3.2.0 is vulnerable to parameter manipulation attacks, allowing an attacker to access restricted areas.

Apache OpenMeetings version 1.0.0 is vulnerable to SQL injection. This allows authenticated users to modify the structure of the existing query and leak the structure of other queries being made by the application in the back-end.

Apache OpenMeetings version 1.0.0 has an overly permissive crossdomain.xml file, allowing Flash content to be loaded from untrusted domains.

Apache OpenMeetings version 1.0.0 is vulnerable to Cross-Site Request Forgery (CSRF) attacks, XSS attacks, click-jacking, and MIME based attacks.

The FileService.importFileByInternalUserId and FileService.importFile SOAP API methods in Apache OpenMeetings before version 3.1.1 improperly use the Java URL class without checking the specified protocol handler, allowing remote attackers to read arbitrary files by attempting to upload a file.

The sendHashByUser function in Apache OpenMeetings before version 3.1.1 generates predictable password reset tokens, making it easier for remote attackers to reset arbitrary user passwords by leveraging knowledge of a user name and the current system time.

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

Apache OpenMeetings version 1.0.0 uses weak cryptographic storage mechanisms. Additionally, the lack of captcha in registration and password reset forms, as well as missing brute force protection in authentication forms, increases the risk.