Show filters
176 Total Results
Displaying 51-60 of 176
Sort by:
Attacker Value
Unknown
CVE-2020-14722
Disclosure Date: July 15, 2020 (last updated November 28, 2024)
Vulnerability in the Oracle Enterprise Communications Broker product of Oracle Communications Applications (component: WebGUI). Supported versions that are affected are 3.0.0-3.2.0. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Enterprise Communications Broker. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Enterprise Communications Broker, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Enterprise Communications Broker accessible data as well as unauthorized read access to a subset of Oracle Enterprise Communications Broker accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Enterprise Communications Broker. CVSS 3.1 Base Score 5.8 (Confidentiality, Integrity and Avai…
0
Attacker Value
Unknown
CVE-2020-8203
Disclosure Date: July 15, 2020 (last updated February 21, 2025)
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
0
Attacker Value
Unknown
CVE-2020-11080
Disclosure Date: June 03, 2020 (last updated February 21, 2025)
In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. The attack causes the CPU to spike at 100%. nghttp2 v1.41.0 fixes this vulnerability. There is a workaround to this vulnerability. Implement nghttp2_on_frame_recv_callback callback, and if received frame is SETTINGS frame and the number of settings entries are large (e.g., > 32), then drop the connection.
0
Attacker Value
Unknown
CVE-2020-7654
Disclosure Date: May 29, 2020 (last updated February 21, 2025)
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.
0
Attacker Value
Unknown
CVE-2020-7648
Disclosure Date: May 29, 2020 (last updated February 21, 2025)
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
0
Attacker Value
Unknown
CVE-2020-7650
Disclosure Date: May 29, 2020 (last updated February 21, 2025)
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
0
Attacker Value
Unknown
CVE-2020-7652
Disclosure Date: May 29, 2020 (last updated February 21, 2025)
All versions of snyk-broker before 4.80.0 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users with access to Snyk's internal network via directory traversal.
0
Attacker Value
Unknown
CVE-2020-7653
Disclosure Date: May 29, 2020 (last updated February 21, 2025)
All versions of snyk-broker before 4.80.0 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users with access to Snyk's internal network by creating symlinks to match whitelisted paths.
0
Attacker Value
Unknown
CVE-2020-7651
Disclosure Date: May 29, 2020 (last updated February 21, 2025)
All versions of snyk-broker before 4.79.0 are vulnerable to Arbitrary File Read. It allows partial file reads for users who have access to Snyk's internal network via patch history from GitHub Commits API.
0
Attacker Value
Unknown
CVE-2020-10726
Disclosure Date: May 20, 2020 (last updated February 21, 2025)
A vulnerability was found in DPDK versions 19.11 and above. A malicious container that has direct access to the vhost-user socket can keep sending VHOST_USER_GET_INFLIGHT_FD messages, causing a resource leak (file descriptors and virtual memory), which may result in a denial of service.
0