CVE-2017-7681
UnknownEPSS 1.29%
Last modified
CVE-2017-7681 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.29% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| 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 |
References
- http://markmail.org/message/j774dp5ro5xmkmg6Mailing List, Third Party Advisory
- http://markmail.org/message/j774dp5ro5xmkmg6Mailing List, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-7681?
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.
How severe is CVE-2017-7681?
Severity scoring for CVE-2017-7681 is pending analysis. The EPSS model estimates a 1.29% probability of exploitation in the next 30 days.
How do I fix CVE-2017-7681?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-7675The HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.0…
- CVE-2017-7676Policy resource matcher in Apache Ranger before 0.7.1 ignore…
- CVE-2017-7677In environments that use external location for hive tables, …
- CVE-2017-7678In Apache Spark before 2.2.0, it is possible for an attacker…
- CVE-2017-7679In Apache httpd 2.2.x before 2.2.33 and 2.4.x before 2.4.26,…
- CVE-2017-7680Apache OpenMeetings 1.0.0 has an overly permissive crossdoma…
- CVE-2017-7682Apache OpenMeetings 3.2.0 is vulnerable to parameter manipul…
- CVE-2017-7683Apache OpenMeetings 1.0.0 displays Tomcat version and detail…
- CVE-2017-7684Apache OpenMeetings 1.0.0 doesn't check contents of files be…
- CVE-2017-7685Apache OpenMeetings 1.0.0 responds to the following insecure…
- CVE-2017-7686Apache Ignite 1.0.0-RC3 to 2.0 uses an update notifier compo…
- CVE-2017-7687When handling a decoding failure for a malformed URL path of…
Are you affected by CVE-2017-7681?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST