First published: Fri Jul 14 2017(Updated: )
Apache OpenMeetings 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.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache OpenMeetings | =1.0.0 | |
Apache OpenMeetings | =2.0 | |
Apache OpenMeetings | =2.1 | |
Apache OpenMeetings | =2.1.1 | |
Apache OpenMeetings | =2.2.0 | |
Apache OpenMeetings | =3.0.0 | |
Apache OpenMeetings | =3.0.1 | |
Apache OpenMeetings | =3.0.2 | |
Apache OpenMeetings | =3.0.3 | |
Apache OpenMeetings | =3.0.4 | |
Apache OpenMeetings | =3.0.5 | |
Apache OpenMeetings | =3.0.6 | |
Apache OpenMeetings | =3.0.7 | |
Apache OpenMeetings | =3.1.0 | |
Apache OpenMeetings | =3.1.1 | |
Apache OpenMeetings | =3.1.2 | |
Apache OpenMeetings | =3.1.3 | |
Apache OpenMeetings | =3.1.4 | |
Apache OpenMeetings | =3.1.5 | |
Apache OpenMeetings | =3.2.0 | |
Apache OpenMeetings | =3.2.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-7681 is categorized as a critical vulnerability due to its potential for SQL injection attacks.
To fix CVE-2017-7681, upgrade Apache OpenMeetings to a version that addresses the SQL injection vulnerability.
CVE-2017-7681 affects Apache OpenMeetings versions 1.0.0, 2.0, 2.1, 2.1.1, 2.2.0, and 3.0.0 to 3.2.1.
CVE-2017-7681 can enable authenticated attackers to modify SQL queries and potentially leak sensitive data.
Exploitation of CVE-2017-7681 can be relatively straightforward for users who have authenticated access to the affected application.