Overview 150,641 matches · 6,879 in Waratek scope · 750 protected · 1,903 exploited · 659 CISA KEV · 24,944 public PoC · 2,543 EPSS ≥ 0.5
150,641matches
6,879in Waratek scope4.6%
750protected0.5%
1,903exploited1.3%
659CISA KEV0.4%
24,944public PoC16.6%
2,543EPSS ≥ 0.51.7%
Protected by Waratek
759
0.5%
Rule in development
1
0.0%
Mitigation candidate
282
0.2%
No exploit published
5,837
3.9%
Outside Waratek scope
2,154
1.4%
Not applicable
133,340
88.5%
Withdrawn CVE
8,268
5.5%
Critical
10,624
7.1%
High
60,164
39.9%
Medium
65,139
43.2%
Low
6,446
4.3%
None
0
0.0%
Unknown
8,268
5.5%
split by
peak 18,938 / year
19882
Not applicable2
High2
not blocked2
Working exploit published1
No public exploit1
19893
Not applicable3
High2
Medium1
not blocked3
No public exploit3
199011
Not applicable11
High8
Medium2
Low1
not blocked11
Working exploit published1
No public exploit10
199115
Not applicable15
High11
Medium4
not blocked15
Working exploit published2
No public exploit13
199214
Not applicable13
Withdrawn CVE1
High12
Low1
Unknown1
not blocked14
No public exploit14
199313
Not applicable13
High8
Medium3
Low2
not blocked13
No public exploit13
199426
Not applicable25
Withdrawn CVE1
High14
Medium10
Low1
Unknown1
not blocked26
Working exploit published6
No public exploit20
199525
Not applicable25
Critical1
High17
Medium6
Low1
not blocked25
Working exploit published5
No public exploit20
199675
No exploit published1
Not applicable73
Withdrawn CVE1
Critical1
High43
Medium21
Low9
Unknown1
not blocked75
Working exploit published18
Forecast only1
No public exploit56
1997253
Not applicable252
Withdrawn CVE1
Critical1
High143
Medium89
Low19
Unknown1
not blocked253
Exploited2
Working exploit published73
Forecast only2
No public exploit176
1998247
Not applicable246
Withdrawn CVE1
Critical1
High137
Medium85
Low23
Unknown1
not blocked247
Exploited1
Working exploit published50
No public exploit196
1999923
No exploit published2
Outside Waratek scope1
Not applicable891
Withdrawn CVE29
Critical3
High423
Medium357
Low111
Unknown29
not blocked923
Exploited2
Working exploit published282
No public exploit639
20001,020
Mitigation candidate7
No exploit published7
Not applicable1,005
Withdrawn CVE1
Critical2
High454
Medium467
Low96
Unknown1
not blocked1,020
Exploited5
Working exploit published427
Forecast only1
No public exploit587
20011,679
Protected by Waratek1
Mitigation candidate4
No exploit published11
Outside Waratek scope10
Not applicable1,650
Withdrawn CVE3
Critical12
High776
Medium706
Low182
Unknown3
blocked by ARMR today1
not blocked1,678
Exploited14
Working exploit published480
Forecast only2
No public exploit1,183
20022,170
Protected by Waratek3
Mitigation candidate8
No exploit published28
Outside Waratek scope4
Not applicable2,113
Withdrawn CVE14
Critical10
High1,023
Medium980
Low143
Unknown14
blocked by ARMR today3
not blocked2,167
Exploited12
Working exploit published545
Forecast only9
No public exploit1,604
20031,548
Protected by Waratek2
Mitigation candidate8
No exploit published31
Outside Waratek scope4
Not applicable1,482
Withdrawn CVE21
Critical9
High674
Medium747
Low97
Unknown21
blocked by ARMR today2
not blocked1,546
Exploited10
Working exploit published499
Forecast only1
No public exploit1,038
20042,479
Protected by Waratek3
Mitigation candidate1
No exploit published25
Outside Waratek scope5
Not applicable2,417
Withdrawn CVE28
Critical10
High973
Medium1,265
Low203
Unknown28
blocked by ARMR today3
not blocked2,476
Exploited21
Working exploit published755
Forecast only1
No public exploit1,702
20055,010
Protected by Waratek3
Mitigation candidate5
No exploit published76
Outside Waratek scope15
Not applicable4,833
Withdrawn CVE78
Critical13
High2,048
Medium2,430
Low441
Unknown78
blocked by ARMR today3
not blocked5,007
Exploited23
Working exploit published1,340
Forecast only11
No public exploit3,636
20066,659
Protected by Waratek8
Mitigation candidate5
No exploit published127
Outside Waratek scope54
Not applicable6,414
Withdrawn CVE51
Critical12
High2,763
Medium3,324
Low509
Unknown51
blocked by ARMR today8
not blocked6,651
Exploited39
Working exploit published2,438
Proof of concept only1
Forecast only6
No public exploit4,175
20076,596
Protected by Waratek7
Mitigation candidate13
No exploit published146
Outside Waratek scope66
Not applicable6,284
Withdrawn CVE80
Critical21
High3,162
Medium3,101
Low232
Unknown80
blocked by ARMR today7
not blocked6,589
Exploited47
Working exploit published2,495
Proof of concept only5
Forecast only5
No public exploit4,044
20085,664
Protected by Waratek7
Mitigation candidate11
No exploit published134
Outside Waratek scope51
Not applicable5,429
Withdrawn CVE32
Critical19
High2,846
Medium2,582
Low185
Unknown32
blocked by ARMR today7
not blocked5,657
Exploited42
Working exploit published2,518
Proof of concept only4
Forecast only9
No public exploit3,091
20095,778
Protected by Waratek9
Mitigation candidate16
No exploit published195
Outside Waratek scope45
Not applicable5,467
Withdrawn CVE46
Critical15
High2,734
Medium2,786
Low197
Unknown46
blocked by ARMR today9
not blocked5,769
Exploited74
Working exploit published2,590
Proof of concept only2
Forecast only3
No public exploit3,109
20104,667
Protected by Waratek9
Mitigation candidate14
No exploit published168
Outside Waratek scope74
Not applicable4,374
Withdrawn CVE28
Critical28
High2,093
Medium2,241
Low277
Unknown28
blocked by ARMR today9
not blocked4,658
Exploited73
Working exploit published1,313
Proof of concept only1
Forecast only9
No public exploit3,271
20114,172
Protected by Waratek6
Mitigation candidate13
No exploit published205
Outside Waratek scope83
Not applicable3,843
Withdrawn CVE22
Critical5
High1,784
Medium2,101
Low260
Unknown22
blocked by ARMR today6
not blocked4,166
Exploited50
Working exploit published691
Proof of concept only5
Forecast only4
No public exploit3,422
20125,351
Protected by Waratek9
Mitigation candidate26
No exploit published291
Outside Waratek scope76
Not applicable4,886
Withdrawn CVE63
Critical21
High1,724
Medium3,035
Low508
Unknown63
blocked by ARMR today9
not blocked5,340
not established2
Exploited59
Working exploit published831
Proof of concept only7
Forecast only46
No public exploit4,408
20135,324
Protected by Waratek26
Mitigation candidate19
No exploit published318
Outside Waratek scope284
Not applicable4,540
Withdrawn CVE137
Critical23
High1,735
Medium2,914
Low515
Unknown137
blocked by ARMR today26
not blocked5,297
not established1
Exploited97
Working exploit published520
Proof of concept only3
Forecast only21
No public exploit4,683
20148,008
Protected by Waratek41
Mitigation candidate13
No exploit published292
Outside Waratek scope233
Not applicable7,349
Withdrawn CVE80
Critical20
High1,938
Medium5,314
Low656
Unknown80
blocked by ARMR today41
not blocked7,967
Exploited97
Working exploit published795
Proof of concept only13
Forecast only16
No public exploit7,087
20156,595
Protected by Waratek33
Mitigation candidate7
No exploit published308
Outside Waratek scope171
Not applicable5,975
Withdrawn CVE101
Critical51
High2,354
Medium3,501
Low588
Unknown101
blocked by ARMR today33
not blocked6,562
Exploited96
Working exploit published647
Proof of concept only16
Forecast only19
No public exploit5,817
20166,517
Protected by Waratek61
Mitigation candidate10
No exploit published479
Outside Waratek scope108
Not applicable5,791
Withdrawn CVE68
Critical887
High2,895
Medium2,446
Low221
Unknown68
blocked by ARMR today59
partly blocked2
not blocked6,455
not established1
Exploited103
Working exploit published429
Proof of concept only27
Forecast only32
No public exploit5,926
201718,113
Protected by Waratek108
Mitigation candidate15
No exploit published701
Outside Waratek scope212
Not applicable13,606
Withdrawn CVE3,471
Critical2,113
High6,608
Medium5,687
Low234
Unknown3,471
blocked by ARMR today104
partly blocked4
not blocked18,005
Exploited212
Working exploit published1,259
Proof of concept only52
Forecast only23
No public exploit16,567
201818,154
Protected by Waratek183
Mitigation candidate23
No exploit published724
Outside Waratek scope205
Not applicable15,375
Withdrawn CVE1,644
Critical2,616
High7,571
Medium6,163
Low160
Unknown1,644
blocked by ARMR today182
partly blocked1
not blocked17,971
Exploited236
Working exploit published1,069
Proof of concept only87
Forecast only34
No public exploit16,728
201918,938
Protected by Waratek123
Rule in development1
Mitigation candidate32
No exploit published797
Outside Waratek scope262
Not applicable16,090
Withdrawn CVE1,633
Critical2,657
High7,227
Medium7,117
Low304
Unknown1,633
blocked by ARMR today121
partly blocked2
not blocked18,813
not established2
Exploited331
Working exploit published783
Proof of concept only126
Forecast only51
No public exploit17,647
202014,592
Protected by Waratek117
Mitigation candidate32
No exploit published771
Outside Waratek scope191
Not applicable12,848
Withdrawn CVE633
Critical2,073
High5,962
Medium5,654
Low270
Unknown633
blocked by ARMR today117
not blocked14,475
Exploited257
Working exploit published502
Proof of concept only112
Forecast only44
No public exploit13,677
19901993199619992002200520082011201420172020
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2020-25770 | Medium | 2020-09-29 | Not applicable | No public exploit | An out-of-bounds read information disclosure vulnerabilities in Trend Micro Apex One may allow a local attacker to disclose sensitive information to an unprivileged account on vulnerable installations of the product. An attacker must first obtain the ability to execute low-privileged code on the target in order to exploit these vulnerabilities. The subs affected in this vulnerability makes it unique compared to similar CVEs such as CVE-2020-24564 and CVE-2020-25771. |
| CVE-2020-24565 | Medium | 2020-09-29 | Not applicable | No public exploit | An out-of-bounds read information disclosure vulnerabilities in Trend Micro Apex One may allow a local attacker to disclose sensitive information to an unprivileged account on vulnerable installations of the product. An attacker must first obtain the ability to execute low-privileged code on the target in order to exploit these vulnerabilities. The subs affected in this vulnerability makes it unique compared to similar CVEs such as CVE-2020-24564 and CVE-2020-25770. |
| CVE-2020-24564 | Medium | 2020-09-29 | Not applicable | No public exploit | An out-of-bounds read information disclosure vulnerabilities in Trend Micro Apex One may allow a local attacker to disclose sensitive information to an unprivileged account on vulnerable installations of the product. An attacker must first obtain the ability to execute low-privileged code on the target in order to exploit these vulnerabilities. The subs affected in this vulnerability makes it unique compared to similar CVEs such as CVE-2020-24565 and CVE-2020-25770. |
| CVE-2020-24563 | High | 2020-09-29 | Not applicable | No public exploit | A vulnerability in Trend Micro Apex One may allow a local attacker to manipulate the process of the security agent unload option (if configured), which then could be manipulated to gain a privilege escalation and code execution. An attacker must first obtain the ability to execute low-privileged code on the target in order to exploit this vulnerability. |
| CVE-2020-24562 | High | 2020-09-29 | Not applicable | No public exploit | A vulnerability in Trend Micro OfficeScan XG SP1 on Microsoft Windows may allow an attacker to create a hard link to any file on the system, which then could be manipulated to gain a privilege escalation and code execution. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. This CVE is similar, but not identical to CVE-2020-24556. |
| CVE-2020-15216 | Medium | 2020-09-29 | Not applicable | No public exploit | In goxmldsig (XML Digital Signatures implemented in pure Go) before version 1.1.0, with a carefully crafted XML file, an attacker can completely bypass signature validation and pass off an altered file as a signed one. A patch is available, all users of goxmldsig should upgrade to at least revision f6188febf0c29d7ffe26a0436212b19cb9615e64 or version 1.1.0 |
| CVE-2020-26121 | High | 2020-09-27 | Not applicable | No public exploit | An issue was discovered in the FileImporter extension for MediaWiki before 1.34.4. An attacker can import a file even when the target page is protected against "page creation" and the attacker should not be able to create it. This occurs because of a mishandled distinction between an upload restriction and a create restriction. An attacker cannot leverage this to overwrite anything, but can leverage this to force a wiki to have a page with a disallowed title. |
| CVE-2020-26120 | Medium | 2020-09-27 | Not applicable | No public exploit | XSS exists in the MobileFrontend extension for MediaWiki before 1.34.4 because section.line is mishandled during regex section line replacement from PageGateway. Using crafted HTML, an attacker can elicit an XSS attack via jQuery's parseHTML method, which can cause image callbacks to fire even without the element being appended to the DOM. |
| CVE-2020-26117 | High | 2020-09-27 | Not applicable | No public exploit | In rfb/CSecurityTLS.cxx and rfb/CSecurityTLS.java in TigerVNC before 1.11.0, viewers mishandle TLS certificate exceptions. They store the certificates as authorities, meaning that the owner of a certificate could impersonate any server after a client had added an exception. |
| CVE-2020-26116 | High | 2020-09-27 | Not applicable | No public exploit | http.client in Python 3.x before 3.5.10, 3.6.x before 3.6.12, 3.7.x before 3.7.9, and 3.8.x before 3.8.5 allows CRLF injection if the attacker controls the HTTP request method, as demonstrated by inserting CR and LF control characters in the first argument of HTTPConnection.request. |
| CVE-2020-25869 | High | 2020-09-27 | Not applicable | No public exploit | An information leak was discovered in MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4. Handling of actor ID does not necessarily use the correct database or correct wiki. |
| CVE-2020-25828 | Medium | 2020-09-27 | Not applicable | No public exploit | An issue was discovered in MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4. The non-jqueryMsg version of mw.message().parse() doesn't escape HTML. This affects both message contents (which are generally safe) and the parameters (which can be based on user input). (When jqueryMsg is loaded, it correctly accepts only whitelisted tags in message contents, and escapes all parameters. Situations with an unloaded jqueryMsg are rare in practice, but can for example occur for Special:SpecialPages on a wiki with no extensions installed.) |
| CVE-2020-25827 | High | 2020-09-27 | Not applicable | No public exploit | An issue was discovered in the OATHAuth extension in MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4. For Wikis using OATHAuth on a farm/cluster (such as via CentralAuth), rate limiting of OATH tokens is only done on a single site level. Thus, multiple requests can be made across many wikis/sites concurrently. |
| CVE-2020-25815 | Medium | 2020-09-27 | Not applicable | No public exploit | An issue was discovered in MediaWiki 1.32.x through 1.34.x before 1.34.4. LogEventList::getFiltersDesc is insecurely using message text to build options names for an HTML multi-select field. The relevant code should use escaped() instead of text(). |
| CVE-2020-25814 | Medium | 2020-09-27 | Not applicable | No public exploit | In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> tag (or it does not have a href attribute, or it's empty, etc.). The actual result is that the object contains an <a href ="javascript... that executes when clicked. |
| CVE-2020-25813 | Medium | 2020-09-27 | Not applicable | No public exploit | In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, Special:UserRights exposes the existence of hidden users. |
| CVE-2020-25812 | Medium | 2020-09-27 | Not applicable | No public exploit | An issue was discovered in MediaWiki 1.34.x before 1.34.4. On Special:Contributions, the NS filter uses unescaped messages as keys in the option key for an HTMLForm specifier. This is vulnerable to a mild XSS if one of those messages is changed to include raw HTML. |
| CVE-2020-7735 | Medium | 2020-09-25 | Not applicable | No public exploit | The package ng-packagr before 10.1.1 are vulnerable to Command Injection via the styleIncludePaths option. |
| CVE-2020-5930 | High | 2020-09-25 | Not applicable | No public exploit | In BIG-IP 15.0.0-15.1.0.4, 14.1.0-14.1.2.7, 13.1.0-13.1.3.3, 12.1.0-12.1.5.2, and 11.6.1-11.6.5.2 and BIG-IQ 5.2.0-7.1.0, unauthenticated attackers can cause disruption of service via undisclosed methods. |
| CVE-2020-5929 | Medium | 2020-09-25 | Not applicable | No public exploit | In versions 13.0.0-13.0.0 HF2, 12.1.0-12.1.2 HF1, and 11.6.1-11.6.2, BIG-IP platforms with Cavium Nitrox SSL hardware acceleration cards, a Virtual Server configured with a Client SSL profile, and using Anonymous (ADH) or Ephemeral (DHE) Diffie-Hellman key exchange and Single DH use option not enabled in the options list may be vulnerable to crafted SSL/TLS Handshakes that may result with a PMS (Pre-Master Secret) that starts in a 0 byte and may lead to a recovery of plaintext messages as BIG-IP TLS/SSL ADH/DHE sends different error messages acting as an oracle. Similar error messages when PMS starts with 0 byte coupled with very precise timing measurement observation may also expose this vulnerability. |
| CVE-2020-4727 | Medium | 2020-09-25 | Not applicable | No public exploit | IBM InfoSphere Information Server 11.7 could allow a remote attacker to hijack the clicking action of the victim. By persuading a victim to visit a malicious Web site, a remote attacker could exploit this vulnerability to hijack the victim's click actions and possibly launch further attacks against the victim. |
| CVE-2020-4531 | Medium | 2020-09-25 | Not applicable | No public exploit | IBM Business Automation Workflow 18.0, 19.0, and 20.0 and IBM Business Process Manager 8.0, 8.5, and 8.6 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system. IBM X-Force ID: 182715. |
| CVE-2020-26115 | Medium | 2020-09-25 | Not applicable | No public exploit | cPanel before 90.0.10 allows self XSS via the Cron Editor interface (SEC-574). |
| CVE-2020-26114 | Medium | 2020-09-25 | Not applicable | No public exploit | cPanel before 90.0.10 allows self XSS via the Cron Jobs interface (SEC-573). |
| CVE-2020-26113 | Medium | 2020-09-25 | Not applicable | No public exploit | cPanel before 90.0.10 allows self XSS via WHM Manage API Tokens interfaces (SEC-569). |
| CVE-2020-26112 | High | 2020-09-25 | Not applicable | No public exploit | The email quota cache in cPanel before 90.0.10 allows overwriting of files. |
| CVE-2020-26111 | Medium | 2020-09-25 | Not applicable | No public exploit | cPanel before 90.0.10 allows self XSS via the WHM Edit DNS Zone interface (SEC-566). |
| CVE-2020-26110 | Medium | 2020-09-25 | Not applicable | No public exploit | cPanel before 88.0.13 allows self XSS via DNS Zone Manager DNSSEC interfaces (SEC-564). |
| CVE-2020-26109 | High | 2020-09-25 | Not applicable | No public exploit | cPanel before 88.0.13 allows bypass of a protection mechanism that attempted to restrict package modification (SEC-557). |
| CVE-2020-26108 | Critical | 2020-09-25 | Not applicable | No public exploit | cPanel before 88.0.13 mishandles file-extension dispatching, leading to code execution (SEC-488). |
| CVE-2020-26107 | High | 2020-09-25 | Not applicable | No public exploit | cPanel before 88.0.3, upon an upgrade, establishes predictable PowerDNS API keys (SEC-561). |
| CVE-2020-26106 | High | 2020-09-25 | Not applicable | No public exploit | cPanel before 88.0.3 has weak permissions (world readable) for the proxy subdomains log file (SEC-558). |
| CVE-2020-26105 | Critical | 2020-09-25 | Not applicable | No public exploit | In cPanel before 88.0.3, insecure chkservd test credentials are used on a templated VM (SEC-554). |
| CVE-2020-26104 | High | 2020-09-25 | Not applicable | No public exploit | In cPanel before 88.0.3, an insecure SRS secret is used on a templated VM (SEC-552). |
| CVE-2020-26103 | High | 2020-09-25 | Not applicable | No public exploit | In cPanel before 88.0.3, an insecure site password is used for Mailman on a templated VM (SEC-551). |
| CVE-2020-26102 | High | 2020-09-25 | Not applicable | No public exploit | In cPanel before 88.0.3, an insecure auth policy API key is used by Dovecot on a templated VM (SEC-550). |
| CVE-2020-26101 | Critical | 2020-09-25 | Not applicable | No public exploit | In cPanel before 88.0.3, insecure RNDC credentials are used for BIND on a templated VM (SEC-549). |
| CVE-2020-26100 | Critical | 2020-09-25 | Not applicable | No public exploit | chsh in cPanel before 88.0.3 allows a Jailshell escape (SEC-497). |
| CVE-2020-26099 | High | 2020-09-25 | Not applicable | No public exploit | cPanel before 88.0.3 allows attackers to bypass the SMTP greylisting protection mechanism (SEC-491). |
| CVE-2020-26098 | Critical | 2020-09-25 | Not applicable | No public exploit | cPanel before 88.0.3 mishandles the Exim filter path, leading to remote code execution (SEC-485). |
| CVE-2020-25749 | Critical | 2020-09-25 | Not applicable | No public exploit | The Telnet service of Rubetek cameras RV-3406, RV-3409, and RV-3411 cameras (firmware versions v342, v339) could allow an remote attacker to take full control of the device with a high-privileged account. The vulnerability exists because a system account has a default and static password. The Telnet service cannot be disabled and this password cannot be changed via standard functionality. |
| CVE-2020-25748 | High | 2020-09-25 | Not applicable | No public exploit | A Cleartext Transmission issue was discovered on Rubetek RV-3406, RV-3409, and RV-3411 cameras (firmware versions v342, v339). Someone in the middle can intercept and modify the video data from the camera, which is transmitted in an unencrypted form. One can also modify responses from NTP and RTSP servers and force the camera to use the changed values. |
| CVE-2020-25747 | Critical | 2020-09-25 | Not applicable | No public exploit | The Telnet service of Rubetek RV-3406, RV-3409, and RV-3411 cameras (firmware versions v342, v339) can allow a remote attacker to gain access to RTSP and ONFIV services without authentication. Thus, the attacker can watch live streams from the camera, rotate the camera, change some settings (brightness, clarity, time), restart the camera, or reset it to factory settings. |
| CVE-2020-25726 | Unknown | 2020-09-25 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none |
| CVE-2020-25625 | Medium | 2020-09-25 | Not applicable | No public exploit | hw/usb/hcd-ohci.c in QEMU 5.0.0 has an infinite loop when a TD list has a loop. |
| CVE-2020-25223 | Critical | 2020-09-25 | Not applicable | Exploited | A remote code execution vulnerability exists in the WebAdmin of Sophos SG UTM before v9.705 MR5, v9.607 MR7, and v9.511 MR11 |
| CVE-2020-25203 | Medium | 2020-09-25 | Not applicable | No public exploit | The Framer Preview application 12 for Android exposes com.framer.viewer.FramerViewActivity to other applications. By calling the intent with the action set to android.intent.action.VIEW, any other application is able to load any website/web content into the application's context, which is shown as a full-screen overlay to the user. |
| CVE-2020-25149 | High | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to directory traversal and local file inclusion due to the fact that there is an unrestricted possibility of loading any file with an inc.php extension. Inclusion of other files (even though limited to the mentioned extension) can lead to Remote Code Execution. This can occur via /device/device=345/?tab=health&metric=../ because of device/health.inc.php. |
| CVE-2020-25148 | Medium | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to Cross-Site Scripting (XSS) due to the fact that it is possible to inject and store malicious JavaScript code within it. this can occur via /iftype/type= because of pages/iftype.inc.php. |
| CVE-2020-25147 | Critical | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to SQL Injection due to the fact that it is possible to inject malicious SQL statements in malformed parameter types. This can occur via username[0] to the default URI, because of includes/authenticate.inc.php. |
| CVE-2020-25146 | Medium | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to Cross-Site Scripting (XSS) due to the fact that it is possible to inject and store malicious JavaScript code within it. This can occur via la_id to the /syslog_rules URI for edit_syslog_rule. |
| CVE-2020-25145 | High | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to directory traversal and local file inclusion due to the fact that there is an unrestricted possibility of loading any file with an inc.php extension. Inclusion of other files (even though limited to the mentioned extension) can lead to Remote Code Execution. This can occur via /device/device=345/?tab=ports&view=../ URIs because of device/port.inc.php. |
| CVE-2020-25144 | High | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to directory traversal and local file inclusion due to the fact that there is an unrestricted possibility of loading any file with an inc.php extension. Inclusion of other files (even though limited to the mentioned extension) can lead to Remote Code Execution. This can occur via /apps/?app=../ URIs. |
| CVE-2020-25143 | High | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to SQL Injection due to the fact that it is possible to inject malicious SQL statements in malformed parameter types. This can occur via /ajax/device_entities.php?entity_type=netscalervsvr&device_id[]= because of /ajax/device_entities.php. |
| CVE-2020-25142 | Medium | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable if any links and forms lack an unpredictable CSRF token. Without such a token, attackers can forge malicious requests, such as for adding Device Settings via the /addsrv URI. |
| CVE-2020-25141 | Medium | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to Cross-Site Scripting (XSS) due to the fact that it is possible to inject and store malicious JavaScript code within it. This can occur via a /device/device=140/tab=wifi/view= URI. |
| CVE-2020-25140 | Medium | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to Cross-Site Scripting (XSS) due to the fact that it is possible to inject and store malicious JavaScript code within it. This can occur in pages/contacts.inc.php. |
| CVE-2020-25139 | Medium | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to Cross-Site Scripting (XSS) due to the fact that it is possible to inject and store malicious JavaScript code within it. This can occur via la_id to the /syslog_rules URI for delete_syslog_rule, because of syslog_rules.inc.php. |
| CVE-2020-25138 | Medium | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to Cross-Site Scripting (XSS) due to the fact that it is possible to inject and store malicious JavaScript code within it. This can occur via /alert_check/action=delete_alert_checker/alert_test_id= because of pages/alert_check.inc.php. |
| CVE-2020-25137 | Medium | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to Cross-Site Scripting (XSS) due to the fact that it is possible to inject and store malicious JavaScript code within it. This can occur via the alert_name or alert_message parameter to the /alert_check URI. |
| CVE-2020-25136 | High | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to directory traversal and local file inclusion due to the fact that there is an unrestricted possibility of loading any file with an inc.php extension. Inclusion of other files (even though limited to the mentioned extension) can lead to Remote Code Execution. This can occur via /device/device=345/?tab=routing&proto=../ URIs to device/routing.inc.php. |
| CVE-2020-25135 | Medium | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to Cross-Site Scripting (XSS) due to the fact that it is possible to inject and store malicious JavaScript code within it. This can occur via the graph_title parameter to the graphs/ URI. |
| CVE-2020-25134 | High | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to directory traversal and local file inclusion due to the fact that there is an unrestricted possibility of loading any file with an inc.php extension. Inclusion of other files (even though limited to the mentioned extension) can lead to Remote Code Execution. This can occur via /settings/?format=../ URIs to pages/settings.inc.php. |
| CVE-2020-25133 | High | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to directory traversal and local file inclusion due to the fact that there is an unrestricted possibility of loading any file with an inc.php extension. Inclusion of other files (even though limited to the mentioned extension) can lead to Remote Code Execution. This can occur via /ports/?format=../ URIs to pages/ports.inc.php. |
| CVE-2020-25132 | Critical | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to SQL Injection due to the fact that it is possible to inject malicious SQL statements in malformed parameter types. Sending the improper variable type Array allows a bypass of core SQL Injection sanitization. Users are able to inject malicious statements in multiple functions. This vulnerability leads to full authentication bypass: any unauthorized user with access to the application is able to exploit this vulnerability. This can occur via the Cookie header to the default URI, within includes/authenticate.inc.php. |
| CVE-2020-25131 | Medium | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to Cross-Site Scripting (XSS) due to the fact that it is possible to inject and store malicious JavaScript code within it. This can occur via the role_name or role_descr parameter to the roles/ URI. |
| CVE-2020-25130 | Medium | 2020-09-25 | Not applicable | No public exploit | An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to SQL Injection due to the fact that it is possible to inject malicious SQL statements in malformed parameter types. Sending an improper variable type of Array allows a bypass of core SQL Injection sanitization. Authenticated users are able to inject malicious SQL queries. This vulnerability leads to full database leak including ckeys that can be used in the authentication process without knowing the username and cleartext password. This can occur via the ajax/actions.php group_id field. |
| CVE-2020-25085 | Medium | 2020-09-25 | Not applicable | No public exploit | QEMU 5.0.0 has a heap-based Buffer Overflow in flatview_read_continue in exec.c because hw/sd/sdhci.c mishandles a write operation in the SDHC_BLKSIZE case. |
| CVE-2020-25084 | Low | 2020-09-25 | Not applicable | No public exploit | QEMU 5.0.0 has a use-after-free in hw/usb/hcd-xhci.c because the usb_packet_map return value is not checked. |
| CVE-2020-24718 | High | 2020-09-25 | Not applicable | No public exploit | bhyve, as used in FreeBSD through 12.1 and illumos (e.g., OmniOS CE through r151034 and OpenIndiana through Hipster 2020.04), does not properly restrict VMCS and VMCB read/write operations, as demonstrated by a root user in a container on an Intel system, who can gain privileges by modifying VMCS_HOST_RIP. |
| CVE-2020-24692 | High | 2020-09-25 | Not applicable | No public exploit | The Ignite portal in Mitel MiContact Center Business before 9.3.0.0 could allow an attacker to execute arbitrary scripts due to insufficient input validation, aka XSS. A successful exploit could allow an attacker to gain access to a user session. |
| CVE-2020-24621 | High | 2020-09-25 | Not applicable | No public exploit | A remote code execution (RCE) vulnerability was discovered in the htmlformentry (aka HTML Form Entry) module before 3.11.0 for OpenMRS. By leveraging path traversal, a malicious Velocity Template Language file could be written to a directory. This file could then be accessed and executed. |
| CVE-2020-24615 | Medium | 2020-09-25 | Not applicable | No public exploit | Pexip Infinity before 24.1 has Improper Input Validation, leading to temporary denial of service via SIP. |
| CVE-2020-24595 | Medium | 2020-09-25 | Not applicable | No public exploit | Mitel MiCloud Management Portal before 6.1 SP5 could allow an attacker, by sending a crafted request, to retrieve sensitive information due to insufficient access control. |
| CVE-2020-24594 | Critical | 2020-09-25 | Not applicable | No public exploit | Mitel MiCloud Management Portal before 6.1 SP5 could allow an unauthenticated attacker to execute arbitrary scripts due to insufficient input validation, aka XSS. A successful exploit could allow an attacker to gain access to a user session. |
| CVE-2020-24593 | High | 2020-09-25 | Not applicable | No public exploit | Mitel MiCloud Management Portal before 6.1 SP5 could allow a remote attacker to conduct a SQL Injection attack and access user credentials due to improper input validation. |
| CVE-2020-24592 | Medium | 2020-09-25 | Not applicable | No public exploit | Mitel MiCloud Management Portal before 6.1 SP5 could allow an attacker, by sending a crafted request, to view system information due to insufficient output sanitization. |
| CVE-2020-23837 | High | 2020-09-25 | Not applicable | No public exploit | A Cross-Site Request Forgery (CSRF) vulnerability in the Multi User plugin 1.8.2 for GetSimple CMS allows remote attackers to add admin (or other) users after an authenticated admin visits a third-party site or clicks on a URL. |
| CVE-2020-19455 | High | 2020-09-25 | Not applicable | No public exploit | SQL injection exists in the jdownloads 3.2.63 component for Joomla! via components/com_jdownloads/helpers/categories.php, order function via the filter_order parameter. |
| CVE-2020-19451 | High | 2020-09-25 | Not applicable | No public exploit | SQL injection exists in the jdownloads 3.2.63 component for Joomla! via com_jdownloads/helpers/jdownloadshelper.php, updateLog function via the X-forwarded-for Header parameter. |
| CVE-2020-19450 | High | 2020-09-25 | Not applicable | No public exploit | SQL injection exists in the jdownloads 3.2.63 component for Joomla! via com_jdownloads/helpers/jdownloadshelper.php, getUserLimits function in the list parameter. |
| CVE-2020-16242 | Medium | 2020-09-25 | Not applicable | No public exploit | The affected Reason S20 Ethernet Switch is vulnerable to cross-site scripting (XSS), which may allow an attacker to trick application users into performing critical application actions that include, but are not limited to, adding and updating accounts. |
| CVE-2020-15521 | Medium | 2020-09-25 | Not applicable | No public exploit | Zoho ManageEngine Applications Manager before 14 build 14730 has no protection against jsp/header.jsp Cross-site Scripting (XSS) . |
| CVE-2020-15394 | Critical | 2020-09-25 | Not applicable | No public exploit | The REST API in Zoho ManageEngine Applications Manager before build 14740 allows an unauthenticated SQL Injection via a crafted request, leading to Remote Code Execution. |
| CVE-2020-15374 | Critical | 2020-09-25 | Not applicable | No public exploit | Rest API in Brocade Fabric OS v8.2.1 through v8.2.1d, and 8.2.2 versions before v8.2.2c is vulnerable to multiple instances of reflected input. |
| CVE-2020-15373 | Critical | 2020-09-25 | Not applicable | No public exploit | Multiple buffer overflow vulnerabilities in REST API in Brocade Fabric OS versions v8.2.1 through v8.2.1d, and 8.2.2 versions before v8.2.2c could allow remote unauthenticated attackers to perform various attacks. |
| CVE-2020-15372 | Medium | 2020-09-25 | Not applicable | No public exploit | A vulnerability in the command-line interface in Brocade Fabric OS before Brocade Fabric OS v8.2.2a1, 8.2.2c, v7.4.2g, v8.2.0_CBN3, v8.2.1e, v8.1.2k, v9.0.0, could allow a local authenticated attacker to modify shell variables, which may lead to an escalation of privileges or bypassing the logging. |
| CVE-2020-15371 | Critical | 2020-09-25 | Not applicable | No public exploit | Brocade Fabric OS versions before Brocade Fabric OS v9.0.0, v8.2.2c, v8.2.1e, v8.1.2k, v8.2.0_CBN3, contains code injection and privilege escalation vulnerability. |
| CVE-2020-15370 | Medium | 2020-09-25 | Not applicable | No public exploit | Brocade Fabric OS versions before Brocade Fabric OS v7.4.2g could allow an authenticated, remote attacker to view a user password in cleartext. The vulnerability is due to incorrectly logging the user password in log files. |
| CVE-2020-15369 | High | 2020-09-25 | Not applicable | No public exploit | Supportlink CLI in Brocade Fabric OS Versions v8.2.1 through v8.2.1d, and 8.2.2 versions before v8.2.2c does not obfuscate the password field, which could expose users’ credentials of the remote server. An authenticated user could obtain the exposed password credentials to gain access to the remote host. |
| CVE-2020-15214 | High | 2020-09-25 | Not applicable | No public exploit | In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a write out bounds / segmentation fault if the segment ids are not sorted. Code assumes that the segment ids are in increasing order, using the last element of the tensor holding them to determine the dimensionality of output tensor. This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array. This usually results in a segmentation fault, but depending on runtime conditions it can provide for a write gadget to be used in future memory corruption-based exploits. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that the segment ids are sorted, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code. |
| CVE-2020-15213 | Medium | 2020-09-25 | Not applicable | No public exploit | In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a denial of service by causing an out of memory allocation in the implementation of segment sum. Since code uses the last element of the tensor holding them to determine the dimensionality of output tensor, attackers can use a very large value to trigger a large allocation. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to limit the maximum value in the segment ids tensor. This only handles the case when the segment ids are stored statically in the model, but a similar validation could be done if the segment ids are generated at runtime, between inference steps. However, if the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code. |
| CVE-2020-15212 | High | 2020-09-25 | Not applicable | No public exploit | In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `output_data` buffer. This might result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other vulnerabilities to create more advanced exploits. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that the segment ids are all positive, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code. |
| CVE-2020-15211 | Medium | 2020-09-25 | Not applicable | No public exploit | In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices for the tensors, indexing into an array of tensors that is owned by the subgraph. This results in a pattern of double array indexing when trying to get the data of each tensor. However, some operators can have some tensors be optional. To handle this scenario, the flatbuffer model uses a negative `-1` value as index for these tensors. This results in special casing during validation at model loading time. Unfortunately, this means that the `-1` index is a valid tensor index for any operator, including those that don't expect optional inputs and including for output tensors. Thus, this allows writing and reading from outside the bounds of heap allocated arrays, although only at a specific offset from the start of these arrays. This results in both read and write gadgets, albeit very limited in scope. The issue is patched in several commits (46d5b0852, 00302787b7, e11f5558, cd31fd0ce, 1970c21, and fff2c83), and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that only operators which accept optional inputs use the `-1` special value and only for the tensors that they expect to be optional. Since this allow-list type approach is erro-prone, we advise upgrading to the patched code. |
| CVE-2020-15210 | Medium | 2020-09-25 | Not applicable | No public exploit | In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and will release patch releases for all versions between 1.15 and 2.3. We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. |
| CVE-2020-15209 | Medium | 2020-09-25 | Not applicable | No public exploit | In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with `nullptr`. However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. The issue is patched in commit 0b5662bc, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. |
| CVE-2020-15208 | Critical | 2020-09-25 | Not applicable | No public exploit | In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors. The issue is patched in commit 8ee24e7949a203d234489f9da2c5bf45a7d5157d, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. |
| CVE-2020-15207 | Critical | 2020-09-25 | Not applicable | No public exploit | In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, to mimic Python's indexing with negative values, TFLite uses `ResolveAxis` to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds. If the `DCHECK` does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption. The issue is patched in commit 2d88f470dea2671b430884260f3626b1fe99830a, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. |
| CVE-2020-15206 | Critical | 2020-09-25 | Not applicable | No public exploit | In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, changing the TensorFlow's `SavedModel` protocol buffer and altering the name of required keys results in segfaults and data corruption while loading the model. This can cause a denial of service in products using `tensorflow-serving` or other inference-as-a-service installments. Fixed were added in commits f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d (both going into TensorFlow 2.2.0 and 2.3.0 but not yet backported to earlier versions). However, this was not enough, as #41097 reports a different failure mode. The issue is patched in commit adf095206f25471e864a8e63a0f1caef53a0e3a6, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. |
| CVE-2020-15205 | Critical | 2020-09-25 | Not applicable | No public exploit | In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `data_splits` argument of `tf.raw_ops.StringNGrams` lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after `ee ff` are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. |