Overview 19,222 matches · 1,138 in Waratek scope · 157 protected · 345 exploited · 146 CISA KEV · 967 public PoC · 317 EPSS ≥ 0.5
19,222matches
1,138in Waratek scope5.9%
157protected0.8%
345exploited1.8%
146CISA KEV0.8%
967public PoC5.0%
317EPSS ≥ 0.51.6%
Protected by Waratek
157
0.8%
Rule in development
0
0.0%
Mitigation candidate
38
0.2%
No exploit published
943
4.9%
Outside Waratek scope
263
1.4%
Not applicable
16,921
88.0%
Withdrawn CVE
900
4.7%
blocked by ARMR today
157
0.8%
partly blocked
0
0.0%
not blocked
19,065
99.2%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 2,209 / month
Jan 201,872
Protected by Waratek18
Mitigation candidate4
No exploit published185
Outside Waratek scope34
Not applicable1,415
Withdrawn CVE216
Critical251
High651
Medium726
Low28
Unknown216
blocked by ARMR today18
not blocked1,854
Exploited27
Working exploit published149
Proof of concept only12
No public exploit1,684
Feb 201,481
Protected by Waratek8
Mitigation candidate2
No exploit published32
Outside Waratek scope15
Not applicable1,337
Withdrawn CVE87
Critical233
High618
Medium520
Low23
Unknown87
blocked by ARMR today8
not blocked1,473
Exploited32
Working exploit published120
Proof of concept only12
Forecast only6
No public exploit1,311
Mar 201,787
Protected by Waratek16
Mitigation candidate8
No exploit published68
Outside Waratek scope7
Not applicable1,655
Withdrawn CVE33
Critical329
High718
Medium674
Low33
Unknown33
blocked by ARMR today16
not blocked1,771
Exploited39
Working exploit published35
Proof of concept only18
Forecast only7
No public exploit1,688
Apr 202,209
Protected by Waratek18
Mitigation candidate5
No exploit published171
Outside Waratek scope24
Not applicable1,969
Withdrawn CVE22
Critical306
High945
Medium877
Low59
Unknown22
blocked by ARMR today18
not blocked2,191
Exploited30
Working exploit published40
Proof of concept only14
Forecast only14
No public exploit2,111
May 201,058
Protected by Waratek14
No exploit published34
Outside Waratek scope24
Not applicable945
Withdrawn CVE41
Critical147
High441
Medium402
Low27
Unknown41
blocked by ARMR today14
not blocked1,044
Exploited22
Working exploit published32
Proof of concept only11
Forecast only2
No public exploit991
Jun 201,856
Protected by Waratek8
Mitigation candidate4
No exploit published29
Outside Waratek scope24
Not applicable1,721
Withdrawn CVE70
Critical225
High823
Medium714
Low24
Unknown70
blocked by ARMR today8
not blocked1,848
Exploited31
Working exploit published36
Proof of concept only19
Forecast only2
No public exploit1,768
Jul 201,453
Protected by Waratek14
Mitigation candidate1
No exploit published167
Outside Waratek scope30
Not applicable1,205
Withdrawn CVE36
Critical235
High577
Medium575
Low30
Unknown36
blocked by ARMR today14
not blocked1,439
Exploited33
Working exploit published33
Proof of concept only11
Forecast only5
No public exploit1,371
Aug 201,239
Protected by Waratek6
Mitigation candidate6
No exploit published18
Outside Waratek scope17
Not applicable1,108
Withdrawn CVE84
Critical139
High523
Medium469
Low24
Unknown84
blocked by ARMR today6
not blocked1,233
Exploited25
Working exploit published24
Proof of concept only5
Forecast only3
No public exploit1,182
Sep 201,637
Protected by Waratek15
Mitigation candidate2
No exploit published67
Outside Waratek scope16
Not applicable1,493
Withdrawn CVE44
Critical208
High666
Medium697
Low22
Unknown44
blocked by ARMR today15
not blocked1,622
Exploited18
Working exploit published33
Proof of concept only10
Forecast only5
No public exploit1,571
Oct 201,574
Protected by Waratek17
Mitigation candidate2
No exploit published107
Outside Waratek scope35
Not applicable1,402
Withdrawn CVE11
Critical218
High699
Medium593
Low53
Unknown11
blocked by ARMR today17
not blocked1,557
Exploited33
Working exploit published29
Proof of concept only17
Forecast only5
No public exploit1,490
Nov 201,492
Protected by Waratek11
Mitigation candidate1
No exploit published39
Outside Waratek scope32
Not applicable1,188
Withdrawn CVE221
Critical193
High560
Medium485
Low33
Unknown221
blocked by ARMR today11
not blocked1,481
Exploited23
Working exploit published31
Proof of concept only12
Forecast only8
No public exploit1,418
Dec 201,564
Protected by Waratek12
Mitigation candidate3
No exploit published26
Outside Waratek scope5
Not applicable1,483
Withdrawn CVE35
Critical296
High561
Medium627
Low45
Unknown35
blocked by ARMR today12
not blocked1,552
Exploited32
Working exploit published40
Proof of concept only14
Forecast only9
No public exploit1,469
Jan 20Feb 20Mar 20Apr 20May 20Jun 20Jul 20Aug 20Sep 20Oct 20Nov 20Dec 20
| 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-13654 | High | 2020-12-31 | No exploit published | Proof of concept only | XWiki Platform before 12.8 mishandles escaping in the property displayer. |
| 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. |