8.8
CVE-2017-7681
- EPSS 0.1%
- Veröffentlicht 17.07.2017 13:18:29
- Zuletzt bearbeitet 20.04.2025 01:37:25
- Quelle security@apache.org
- Teams Watchlist Login
- Unerledigt Login
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.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Apache ≫ Openmeetings Version1.0.0
Apache ≫ Openmeetings Version2.0
Apache ≫ Openmeetings Version2.1
Apache ≫ Openmeetings Version2.1.1
Apache ≫ Openmeetings Version2.2.0
Apache ≫ Openmeetings Version3.0.0
Apache ≫ Openmeetings Version3.0.1
Apache ≫ Openmeetings Version3.0.2
Apache ≫ Openmeetings Version3.0.3
Apache ≫ Openmeetings Version3.0.4
Apache ≫ Openmeetings Version3.0.5
Apache ≫ Openmeetings Version3.0.6
Apache ≫ Openmeetings Version3.0.7
Apache ≫ Openmeetings Version3.1.0
Apache ≫ Openmeetings Version3.1.1
Apache ≫ Openmeetings Version3.1.2
Apache ≫ Openmeetings Version3.1.3
Apache ≫ Openmeetings Version3.1.4
Apache ≫ Openmeetings Version3.1.5
Apache ≫ Openmeetings Version3.2.0
Apache ≫ Openmeetings Version3.2.1
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Typ | Quelle | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 0.1% | 0.243 |
Quelle | Base Score | Exploit Score | Impact Score | Vector String |
---|---|---|---|---|
nvd@nist.gov | 8.8 | 2.8 | 5.9 |
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
|
nvd@nist.gov | 6.5 | 8 | 6.4 |
AV:N/AC:L/Au:S/C:P/I:P/A:P
|
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.