Overview 128,941 matches · 6,600 in Waratek scope · 614 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
128,941matches
6,600in Waratek scope5.1%
614protected0.5%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
615
0.5%
Rule in development
0
0.0%
Mitigation candidate
2
0.0%
No exploit published
5,983
4.6%
Outside Waratek scope
2,089
1.6%
Not applicable
111,820
86.7%
Withdrawn CVE
8,432
6.5%
Critical
9,668
7.5%
High
48,591
37.7%
Medium
56,294
43.7%
Low
5,956
4.6%
None
0
0.0%
Unknown
8,432
6.5%
blocked by ARMR today
614
0.5%
partly blocked
1
0.0%
not blocked
128,326
99.5%
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
128,941
100.0%
split by
peak 18,054 / year
19881
Not applicable1
High1
not blocked1
No public exploit1
19893
Not applicable3
High2
Medium1
not blocked3
No public exploit3
199010
Not applicable10
High8
Medium1
Low1
not blocked10
No public exploit10
199113
Not applicable13
High9
Medium4
not blocked13
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
199420
Not applicable19
Withdrawn CVE1
High11
Medium8
Unknown1
not blocked20
No public exploit20
199520
Not applicable20
High15
Medium4
Low1
not blocked20
No public exploit20
199656
No exploit published1
Not applicable55
Critical1
High30
Medium16
Low9
not blocked56
No public exploit56
1997176
Not applicable175
Withdrawn CVE1
Critical1
High90
Medium71
Low13
Unknown1
not blocked176
No public exploit176
1998196
Not applicable195
Withdrawn CVE1
High103
Medium74
Low18
Unknown1
not blocked196
No public exploit196
1999639
No exploit published2
Not applicable609
Withdrawn CVE28
Critical1
High289
Medium238
Low83
Unknown28
not blocked639
No public exploit639
2000587
No exploit published6
Not applicable580
Withdrawn CVE1
Critical1
High253
Medium270
Low62
Unknown1
not blocked587
No public exploit587
20011,183
Protected by Waratek1
No exploit published11
Outside Waratek scope8
Not applicable1,160
Withdrawn CVE3
Critical8
High546
Medium482
Low144
Unknown3
blocked by ARMR today1
not blocked1,182
No public exploit1,183
20021,604
Protected by Waratek3
No exploit published26
Outside Waratek scope3
Not applicable1,560
Withdrawn CVE12
Critical6
High735
Medium728
Low123
Unknown12
blocked by ARMR today3
not blocked1,601
No public exploit1,604
20031,038
Protected by Waratek1
No exploit published31
Outside Waratek scope3
Not applicable983
Withdrawn CVE20
Critical5
High428
Medium504
Low81
Unknown20
blocked by ARMR today1
not blocked1,037
No public exploit1,038
20041,702
Protected by Waratek2
No exploit published25
Outside Waratek scope5
Not applicable1,642
Withdrawn CVE28
Critical6
High661
Medium840
Low167
Unknown28
blocked by ARMR today2
not blocked1,700
No public exploit1,702
20053,636
Protected by Waratek2
No exploit published76
Outside Waratek scope12
Not applicable3,473
Withdrawn CVE73
Critical8
High1,374
Medium1,794
Low387
Unknown73
blocked by ARMR today2
not blocked3,634
No public exploit3,636
20064,175
Protected by Waratek6
No exploit published127
Outside Waratek scope50
Not applicable3,944
Withdrawn CVE48
Critical8
High1,535
Medium2,175
Low409
Unknown48
blocked by ARMR today6
not blocked4,169
No public exploit4,175
20074,044
Protected by Waratek5
No exploit published146
Outside Waratek scope58
Not applicable3,758
Withdrawn CVE77
Critical11
High1,720
Medium2,034
Low202
Unknown77
blocked by ARMR today5
not blocked4,039
No public exploit4,044
20083,091
Protected by Waratek2
No exploit published134
Outside Waratek scope47
Not applicable2,881
Withdrawn CVE27
Critical13
High1,311
Medium1,585
Low155
Unknown27
blocked by ARMR today2
not blocked3,089
No public exploit3,091
20093,109
Protected by Waratek5
No exploit published195
Outside Waratek scope38
Not applicable2,831
Withdrawn CVE40
Critical8
High1,256
Medium1,642
Low163
Unknown40
blocked by ARMR today5
not blocked3,104
No public exploit3,109
20103,271
Protected by Waratek4
No exploit published167
Outside Waratek scope64
Not applicable3,010
Withdrawn CVE26
Critical16
High1,304
Medium1,677
Low248
Unknown26
blocked by ARMR today4
not blocked3,267
No public exploit3,271
20113,422
Protected by Waratek3
No exploit published205
Outside Waratek scope79
Not applicable3,116
Withdrawn CVE19
High1,363
Medium1,794
Low246
Unknown19
blocked by ARMR today3
not blocked3,419
No public exploit3,422
20124,408
Protected by Waratek6
No exploit published291
Outside Waratek scope65
Not applicable3,988
Withdrawn CVE58
Critical11
High1,369
Medium2,496
Low474
Unknown58
blocked by ARMR today6
not blocked4,402
No public exploit4,408
20134,683
Protected by Waratek16
Mitigation candidate1
No exploit published316
Outside Waratek scope263
Not applicable3,970
Withdrawn CVE117
Critical13
High1,415
Medium2,647
Low491
Unknown117
blocked by ARMR today16
not blocked4,667
No public exploit4,683
20147,087
Protected by Waratek32
No exploit published292
Outside Waratek scope233
Not applicable6,461
Withdrawn CVE69
Critical9
High1,526
Medium4,856
Low627
Unknown69
blocked by ARMR today32
not blocked7,055
No public exploit7,087
20155,817
Protected by Waratek26
No exploit published307
Outside Waratek scope164
Not applicable5,224
Withdrawn CVE96
Critical32
High1,928
Medium3,208
Low553
Unknown96
blocked by ARMR today26
not blocked5,791
No public exploit5,817
20165,926
Protected by Waratek40
No exploit published478
Outside Waratek scope108
Not applicable5,236
Withdrawn CVE64
Critical795
High2,559
Medium2,293
Low215
Unknown64
blocked by ARMR today40
not blocked5,886
No public exploit5,926
201716,567
Protected by Waratek81
No exploit published700
Outside Waratek scope208
Not applicable12,118
Withdrawn CVE3,460
Critical1,707
High5,857
Medium5,314
Low229
Unknown3,460
blocked by ARMR today80
partly blocked1
not blocked16,486
No public exploit16,567
201816,728
Protected by Waratek159
No exploit published724
Outside Waratek scope195
Not applicable14,012
Withdrawn CVE1,638
Critical2,236
High6,959
Medium5,743
Low152
Unknown1,638
blocked by ARMR today159
not blocked16,569
No public exploit16,728
201917,648
Protected by Waratek94
No exploit published795
Outside Waratek scope247
Not applicable14,883
Withdrawn CVE1,629
Critical2,331
High6,650
Medium6,735
Low303
Unknown1,629
blocked by ARMR today94
not blocked17,554
No public exploit17,648
202018,054
Protected by Waratek127
Mitigation candidate1
No exploit published928
Outside Waratek scope239
Not applicable15,864
Withdrawn CVE895
Critical2,441
High7,264
Medium7,057
Low397
Unknown895
blocked by ARMR today127
not blocked17,927
No public exploit18,054
19901993199619992002200520082011201420172020
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2020-35931 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in Foxit Reader before 10.1.1 (and before 4.1.1 on macOS) and PhantomPDF before 9.7.5 and 10.x before 10.1.1 (and before 4.1.1 on macOS). An attacker can spoof a certified PDF document via an Evil Annotation Attack because the products fail to consider a null value for a Subtype entry of the Annotation dictionary, in an incremental update. |
| CVE-2020-35930 | Medium | 2020-12-31 | Not applicable | No public exploit | Seo Panel 4.8.0 allows stored XSS by an Authenticated User via the url parameter, as demonstrated by the seo/seopanel/websites.php URI. |
| CVE-2020-35928 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the concread crate before 0.2.6 for Rust. Attackers can cause an ARCache<K,V> data race by sending types that do not implement Send/Sync. |
| CVE-2020-35927 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the thex crate through 2020-12-08 for Rust. Thex<T> allows cross-thread data races of non-Send types. |
| CVE-2020-35926 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the nanorand crate before 0.5.1 for Rust. It caused any random number generator (even ChaCha) to return all zeroes because integer truncation was mishandled. |
| CVE-2020-35925 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the magnetic crate before 2.0.1 for Rust. MPMCConsumer and MPMCProducer allow cross-thread sending of a non-Send type. |
| CVE-2020-35924 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the try-mutex crate before 0.3.0 for Rust. TryMutex<T> allows cross-thread sending of a non-Send type. |
| CVE-2020-35923 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the ordered-float crate before 1.1.1 and 2.x before 2.0.1 for Rust. A NotNan value can contain a NaN. |
| CVE-2020-35922 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the mio crate before 0.7.6 for Rust. It has false expectations about the std::net::SocketAddr memory representation. |
| CVE-2020-35921 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the miow crate before 0.3.6 for Rust. It has false expectations about the std::net::SocketAddr memory representation. |
| CVE-2020-35920 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the socket2 crate before 0.3.16 for Rust. It has false expectations about the std::net::SocketAddr memory representation. |
| CVE-2020-35919 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the net2 crate before 0.2.36 for Rust. It has false expectations about the std::net::SocketAddr memory representation. |
| CVE-2020-35918 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the branca crate before 0.10.0 for Rust. Decoding tokens (with invalid base62 data) can panic. |
| CVE-2020-35917 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the pyo3 crate before 0.12.4 for Rust. There is a reference-counting error and use-after-free in From<Py<T>>. |
| CVE-2020-35916 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the image crate before 0.23.12 for Rust. A Mutable reference has immutable provenance. (In the case of LLVM, the IR may be always correct.) |
| CVE-2020-35915 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the futures-intrusive crate before 0.4.0 for Rust. GenericMutexGuard allows cross-thread data races of non-Sync types. |
| CVE-2020-35914 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness. |
| CVE-2020-35913 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness. |
| CVE-2020-35912 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness. |
| CVE-2020-35911 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness. |
| CVE-2020-35910 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness. |
| CVE-2020-35909 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the multihash crate before 0.11.3 for Rust. The from_slice parsing code can panic via unsanitized data from a network server. |
| CVE-2020-35908 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the futures-util crate before 0.3.2 for Rust. FuturesUnordered can lead to data corruption because Sync is mishandled. |
| CVE-2020-35907 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the futures-task crate before 0.3.5 for Rust. futures_task::noop_waker_ref allows a NULL pointer dereference. |
| CVE-2020-35906 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the futures-task crate before 0.3.6 for Rust. futures_task::waker may cause a use-after-free in a non-static type situation. |
| CVE-2020-35905 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the futures-util crate before 0.3.7 for Rust. MutexGuard::map can cause a data race for certain closure situations (in safe code). |
| CVE-2020-35904 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the crossbeam-channel crate before 0.4.4 for Rust. It has incorrect expectations about the relationship between the memory allocation and how many iterator elements there are. |
| CVE-2020-35903 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the dync crate before 0.5.0 for Rust. VecCopy allows misaligned element access because u8 is not always the type in question. |
| CVE-2020-35902 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the actix-codec crate before 0.3.0-beta.1 for Rust. There is a use-after-free in Framed. |
| CVE-2020-35901 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the actix-http crate before 2.0.0-alpha.1 for Rust. There is a use-after-free in BodyStream. |
| CVE-2020-35900 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the array-queue crate through 2020-09-26 for Rust. A pop_back() call may lead to a use-after-free. |
| CVE-2020-35899 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the actix-service crate before 1.0.6 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data. |
| CVE-2020-35898 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the actix-utils crate before 2.0.0 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data. |
| CVE-2020-35897 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the atom crate before 0.3.6 for Rust. An unsafe Send implementation allows a cross-thread data race. |
| CVE-2020-35896 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the ws crate through 2020-09-25 for Rust. The outgoing buffer is not properly limited, leading to a remote memory-consumption attack. |
| CVE-2020-35895 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the stack crate before 0.3.1 for Rust. ArrayVec has an out-of-bounds write via element insertion. |
| CVE-2020-35894 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the obstack crate before 0.1.4 for Rust. Unaligned references can occur. |
| CVE-2020-35893 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the simple-slab crate before 0.3.3 for Rust. remove() has an off-by-one error, causing memory leakage and a drop of uninitialized memory. |
| CVE-2020-35892 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the simple-slab crate before 0.3.3 for Rust. index() allows an out-of-bounds read. |
| CVE-2020-35891 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the ordnung crate through 2020-09-03 for Rust. compact::Vec violates memory safety via a remove() double free. |
| CVE-2020-35890 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the ordnung crate through 2020-09-03 for Rust. compact::Vec violates memory safety via out-of-bounds access for large capacity. |
| CVE-2020-35889 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the crayon crate through 2020-08-31 for Rust. A TOCTOU issue has a resultant memory safety violation via HandleLike. |
| CVE-2020-35888 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the arr crate through 2020-08-25 for Rust. Uninitialized memory is dropped by Array::new_from_template. |
| CVE-2020-35887 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the arr crate through 2020-08-25 for Rust. There is a buffer overflow in Index and IndexMut. |
| CVE-2020-35886 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the arr crate through 2020-08-25 for Rust. An attacker can smuggle non-Sync/Send types across a thread boundary to cause a data race. |
| CVE-2020-35885 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the alpm-rs crate through 2020-08-20 for Rust. StrcCtx performs improper memory deallocation. |
| CVE-2020-35884 | Medium | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the tiny_http crate through 2020-06-16 for Rust. HTTP Request smuggling can occur via a malformed Transfer-Encoding header. |
| CVE-2020-35883 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the mozwire crate through 2020-08-18 for Rust. A ../ directory-traversal situation allows overwriting local files that have .conf at the end of the filename. |
| CVE-2020-35882 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the rocket crate before 0.4.5 for Rust. LocalRequest::clone creates more than one mutable references to the same object, possibly causing a data race. |
| CVE-2020-35881 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the traitobject crate through 2020-06-01 for Rust. It has false expectations about fat pointers, possibly causing memory corruption in, for example, Rust 2.x. |
| CVE-2020-35880 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the bigint crate through 2020-05-07 for Rust. It allows a soundness violation. |
| CVE-2020-35879 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the rulinalg crate through 2020-02-11 for Rust. There are incorrect lifetime-boundary definitions for RowMut::raw_slice and RowMut::raw_slice_mut. |
| CVE-2020-35878 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the ozone crate through 2020-07-04 for Rust. Memory safety is violated because of the dropping of uninitialized memory. |
| CVE-2020-35877 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the ozone crate through 2020-07-04 for Rust. Memory safety is violated because of out-of-bounds access. |
| CVE-2020-35876 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the rio crate through 2020-05-11 for Rust. A struct can be leaked, allowing attackers to obtain sensitive information, cause a use-after-free, or cause a data race. |
| CVE-2020-35875 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the tokio-rustls crate before 0.13.1 for Rust. Excessive memory usage may occur when data arrives quickly. |
| CVE-2020-35874 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the internment crate through 2020-05-28 for Rust. ArcIntern::drop has a race condition and resultant use-after-free. |
| CVE-2020-35873 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because sessions.rs has a use-after-free. |
| CVE-2020-35872 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via the repr(Rust) type. |
| CVE-2020-35871 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API data race. |
| CVE-2020-35870 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API use-after-free. |
| CVE-2020-35869 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because rusqlite::trace::log mishandles format strings. |
| CVE-2020-35868 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via UnlockNotification. |
| CVE-2020-35867 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via create_module. |
| CVE-2020-35866 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via VTab / VTabCursor. |
| CVE-2020-35865 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the os_str_bytes crate before 2.0.0 for Rust. It has false expectations about char::from_u32_unchecked behavior. |
| CVE-2020-35864 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the flatbuffers crate through 2020-04-11 for Rust. read_scalar (and read_scalar_at) can transmute values without unsafe blocks. |
| CVE-2020-35863 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the hyper crate before 0.12.34 for Rust. HTTP request smuggling can occur. Remote code execution can occur in certain situations with an HTTP server on the loopback interface. |
| CVE-2020-35862 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the bitvec crate before 0.17.4 for Rust. BitVec to BitBox conversion leads to a use-after-free or double free. |
| CVE-2020-35861 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the bumpalo crate before 3.2.1 for Rust. The realloc feature allows the reading of unknown memory. Attackers can potentially read cryptographic keys. |
| CVE-2020-35860 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the cbox crate through 2020-03-19 for Rust. The CBox API allows dereferencing raw pointers without a requirement for unsafe code. |
| CVE-2020-35859 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the lucet-runtime-internals crate before 0.5.1 for Rust. It mishandles sigstack allocation. Guest programs may be able to obtain sensitive information, or guest programs can experience memory corruption. |
| CVE-2020-35858 | Critical | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the prost crate before 0.6.1 for Rust. There is stack consumption via a crafted message, causing a denial of service (e.g., x86) or possibly remote code execution (e.g., ARM). |
| CVE-2020-35857 | High | 2020-12-31 | Not applicable | No public exploit | An issue was discovered in the trust-dns-server crate before 0.18.1 for Rust. DNS MX and SRV null targets are mishandled, causing stack consumption. |
| CVE-2020-35851 | Critical | 2020-12-31 | Not applicable | No public exploit | HGiga MailSherlock does not validate specific parameters properly. Attackers can use the vulnerability to launch Command inject attacks remotely and execute arbitrary commands of the system. |
| CVE-2020-35743 | High | 2020-12-31 | Not applicable | No public exploit | HGiga MailSherlock contains a SQL injection flaw. Attackers can inject and launch SQL commands in a URL parameter of specific cgi pages. |
| CVE-2020-35742 | High | 2020-12-31 | Not applicable | No public exploit | HGiga MailSherlock contains a vulnerability of SQL Injection. Attackers can inject and launch SQL commands in a URL parameter. |
| CVE-2020-35741 | High | 2020-12-31 | Not applicable | No public exploit | HGiga MailSherlock does not validate user parameters on multiple login pages. Attackers can use the vulnerability to inject JavaScript syntax for XSS attacks. |
| CVE-2020-35740 | High | 2020-12-31 | Not applicable | No public exploit | HGiga MailSherlock does not validate specific URL parameters properly that allows attackers to inject JavaScript syntax for XSS attacks. |
| CVE-2020-26291 | Medium | 2020-12-31 | Not applicable | No public exploit | URI.js is a javascript URL mutation library (npm package urijs). In URI.js before version 1.19.4, the hostname can be spoofed by using a backslash (`\`) character followed by an at (`@`) character. If the hostname is used in security decisions, the decision may be incorrect. Depending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior. For example the URL `https://expected-example.com\@observed-example.com` will incorrectly return `observed-example.com` if using an affected version. Patched versions correctly return `expected-example.com`. Patched versions match the behavior of other parsers which implement the WHATWG URL specification, including web browsers and Node's built-in URL class. Version 1.19.4 is patched against all known payload variants. Version 1.19.3 has a partial patch but is still vulnerable to a payload variant.] |
| CVE-2020-26165 | High | 2020-12-31 | Not applicable | No public exploit | qdPM through 9.1 allows PHP Object Injection via timeReportActions::executeExport in core/apps/qdPM/modules/timeReport/actions/actions.class.php because unserialize is used. |
| CVE-2020-25850 | High | 2020-12-31 | Not applicable | No public exploit | The function, view the source code, of HGiga MailSherlock does not validate specific characters. Remote attackers can use this flaw to download arbitrary system files. |
| CVE-2020-25848 | Critical | 2020-12-31 | Not applicable | No public exploit | HGiga MailSherlock contains weak authentication flaw that attackers grant privilege remotely with default password generation mechanism. |
| CVE-2020-25846 | High | 2020-12-31 | Not applicable | No public exploit | The digest generation function of NHIServiSignAdapter has not been verified for source file path, which leads to the SMB request being redirected to a malicious host, resulting in the leakage of user's credential. |
| CVE-2020-25845 | High | 2020-12-31 | Not applicable | No public exploit | Multiple functions of NHIServiSignAdapter failed to verify the users’ file path, which leads to the SMB request being redirected to a malicious host, resulting in the leakage of user's credential. |
| CVE-2020-25844 | Critical | 2020-12-31 | Not applicable | No public exploit | The digest generation function of NHIServiSignAdapter has not been verified for parameter’s length, which leads to a stack overflow loophole. Remote attackers can use the leak to execute code without privilege. |
| CVE-2020-25843 | Critical | 2020-12-31 | Not applicable | No public exploit | NHIServiSignAdapter fails to verify the length of digital credential files’ path which leads to a heap overflow loophole. Remote attackers can use the leak to execute code without privilege. |
| CVE-2020-25842 | High | 2020-12-31 | Not applicable | No public exploit | The encryption function of NHIServiSignAdapter fail to verify the file path input by users. Remote attacker can access arbitrary files through the flaw without privilege. |
| CVE-2020-25799 | Medium | 2020-12-31 | Not applicable | No public exploit | LimeSurvey 3.21.1 is affected by cross-site scripting (XSS) in the Quota component of the Survey page. When the survey quota being viewed, e.g. by an administrative user, the JavaScript code will be executed in the browser. |
| CVE-2020-25797 | Medium | 2020-12-31 | Not applicable | No public exploit | LimeSurvey 3.21.1 is affected by cross-site scripting (XSS) in the Add Participants Function (First and last name parameters). When the survey participant being edited, e.g. by an administrative user, the JavaScript code will be executed in the browser. |
| CVE-2020-19664 | High | 2020-12-31 | Not applicable | No public exploit | DrayTek Vigor2960 1.5.1 allows remote command execution via shell metacharacters in a toLogin2FA action to mainfunction.cgi. |
| CVE-2020-17363 | Critical | 2020-12-31 | Not applicable | No public exploit | USVN (aka User-friendly SVN) before 1.0.9 allows remote code execution via shell metacharacters in the number_start or number_end parameter to LastHundredRequest (aka lasthundredrequestAction) in the Timeline module. NOTE: this may overlap CVE-2020-25069. |
| CVE-2020-16132 | Unknown | 2020-12-31 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2020-24240. Reason: This candidate is a reservation duplicate of CVE-2020-24240. Notes: All CVE users should reference CVE-2020-24240 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage |
| CVE-2020-12658 | Critical | 2020-12-31 | Not applicable | No public exploit | gssproxy (aka gss-proxy) before 0.8.3 does not unlock cond_mutex before pthread exit in gp_worker_main() in gp_workers.c. NOTE: An upstream comment states "We are already on a shutdown path when running the code in question, so a DoS there doesn't make any sense, and there has been no additional information provided us (as upstream) to indicate why this would be a problem. |
| CVE-2020-11947 | Low | 2020-12-31 | Not applicable | No public exploit | iscsi_aio_ioctl_cb in block/iscsi.c in QEMU 4.1.0 has a heap-based buffer over-read that may disclose unrelated information from process memory to an attacker. |
| CVE-2020-11835 | Medium | 2020-12-31 | Not applicable | No public exploit | In /SM8250_Q_Master/android/vendor/oppo_charger/oppo/charger_ic/oppo_da9313.c, failure to check the parameter buf in the function proc_work_mode_write in proc_work_mode_write causes a vulnerability. |
| CVE-2020-11834 | Medium | 2020-12-31 | Not applicable | No public exploit | In /SM8250_Q_Master/android/vendor/oppo_charger/oppo/oppo_vooc.c, the function proc_fastchg_fw_update_write in proc_fastchg_fw_update_write does not check the parameter len, resulting in a vulnerability. |
| CVE-2020-11833 | Medium | 2020-12-31 | Not applicable | No public exploit | In /SM8250_Q_Master/android/vendor/oppo_charger/oppo/charger_ic/oppo_mp2650.c, the function mp2650_data_log_write in mp2650_data_log_write does not check the parameter len which causes a vulnerability. |
| CVE-2020-11832 | Medium | 2020-12-31 | Not applicable | No public exploit | In functions charging_limit_current_write and charging_limit_time_write in /SM8250_Q_Master/android/vendor/oppo_charger/oppo/oppo_charger.c have not checked the parameters, which causes a vulnerability. |
| CVE-2019-7726 | Critical | 2020-12-31 | Not applicable | No public exploit | modules/banners/funcs/click.php in NukeViet before 4.3.04 has a SQL INSERT statement with raw header data from an HTTP request (e.g., Referer and User-Agent). |