Overview 12 matches · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
12matches
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
12
100.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
12
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
12
100.0%
split by
peak 9 / month
Apr 162
No exploit published2
High1
Medium1
not blocked2
No public exploit2
May 160
Jun 160
Jul 160
Aug 161
No exploit published1
Medium1
not blocked1
No public exploit1
Sep 160
Oct 160
Nov 160
Dec 160
Jan 170
Feb 170
Mar 170
Apr 170
May 170
Jun 170
Jul 179
No exploit published9
Critical1
High6
Medium2
not blocked9
No public exploit9
May 16Jul 16Sep 16Nov 16Jan 17Mar 17May 17Jul 17
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2017-7688 | High | 2017-07-17 | No exploit published | No public exploit | Apache OpenMeetings 1.0.0 updates user password in insecure manner. |
| CVE-2017-7685 | Medium | 2017-07-17 | No exploit published | No public exploit | Apache OpenMeetings 1.0.0 responds to the following insecure HTTP methods: PUT, DELETE, HEAD, and PATCH. |
| CVE-2017-7684 | High | 2017-07-17 | No exploit published | No public exploit | Apache OpenMeetings 1.0.0 doesn't check contents of files being uploaded. An attacker can cause a denial of service by uploading multiple large files to the server. |
| CVE-2017-7683 | High | 2017-07-17 | No exploit published | No public exploit | Apache OpenMeetings 1.0.0 displays Tomcat version and detailed error stack trace, which is not secure. |
| CVE-2017-7682 | High | 2017-07-17 | No exploit published | No public exploit | Apache OpenMeetings 3.2.0 is vulnerable to parameter manipulation attacks, as a result attacker has access to restricted areas. |
| CVE-2017-7680 | High | 2017-07-17 | No exploit published | No public exploit | Apache OpenMeetings 1.0.0 has an overly permissive crossdomain.xml file. This allows for flash content to be loaded from untrusted domains. |
| CVE-2017-7673 | Critical | 2017-07-17 | No exploit published | No public exploit | Apache OpenMeetings 1.0.0 uses not very strong cryptographic storage, captcha is not used in registration and forget password dialogs and auth forms missing brute force protection. |
| CVE-2017-7666 | High | 2017-07-17 | No exploit published | No public exploit | Apache OpenMeetings 1.0.0 is vulnerable to Cross-Site Request Forgery (CSRF) attacks, XSS attacks, click-jacking, and MIME based attacks. |
| CVE-2017-7663 | Medium | 2017-07-17 | No exploit published | No public exploit | Both global and Room chat are vulnerable to XSS attack in Apache OpenMeetings 3.2.0. |
| CVE-2016-3089 | Medium | 2016-08-19 | No exploit published | No public exploit | Cross-site scripting (XSS) vulnerability in the SWF panel in Apache OpenMeetings before 3.1.2 allows remote attackers to inject arbitrary web script or HTML via the swf parameter. |
| CVE-2016-2164 | High | 2016-04-11 | No exploit published | No public exploit | The (1) FileService.importFileByInternalUserId and (2) FileService.importFile SOAP API methods in Apache OpenMeetings before 3.1.1 improperly use the Java URL class without checking the specified protocol handler, which allows remote attackers to read arbitrary files by attempting to upload a file. |
| CVE-2016-2163 | Medium | 2016-04-11 | No exploit published | No public exploit | Cross-site scripting (XSS) vulnerability in Apache OpenMeetings before 3.1.1 allows remote attackers to inject arbitrary web script or HTML via the event description when creating an event. |