Show filters
152 Total Results
Displaying 121-130 of 152
Sort by:
Attacker Value
Unknown
CVE-2020-1592
Disclosure Date: September 11, 2020 (last updated February 22, 2025)
<p>An information disclosure vulnerability exists when the Windows kernel improperly initializes objects in memory.</p>
<p>To exploit this vulnerability, an authenticated attacker could run a specially crafted application. An attacker who successfully exploited this vulnerability could obtain information to further compromise the user’s system.</p>
<p>The update addresses the vulnerability by correcting how the Windows kernel initializes objects in memory.</p>
0
Attacker Value
Unknown
CVE-2020-24996
Disclosure Date: September 03, 2020 (last updated February 22, 2025)
There is an invalid memory access in the function TextString::~TextString() located in Catalog.cc in Xpdf 4.0.2. It can be triggered by (for example) sending a crafted pdf file to the pdftohtml binary, which allows a remote attacker to cause a Denial of Service (Segmentation fault) or possibly have unspecified other impact.
0
Attacker Value
Unknown
CVE-2020-12301
Disclosure Date: August 13, 2020 (last updated February 21, 2025)
Improper initialization in BIOS firmware for Intel(R) Server Board Families S2600ST, S2600BP and S2600WF may allow a privileged user to potentially enable escalation of privilege via local access.
0
Attacker Value
Unknown
CVE-2020-8918
Disclosure Date: August 11, 2020 (last updated February 21, 2025)
An improperly initialized 'migrationAuth' value in Google's go-tpm TPM1.2 library versions prior to 0.3.0 can lead an eavesdropping attacker to discover the auth value for a key created with CreateWrapKey. An attacker listening in on the channel can collect both 'encUsageAuth' and 'encMigrationAuth', and then can calculate 'usageAuth ^ encMigrationAuth' as the 'migrationAuth' can be guessed for all keys created with CreateWrapKey. TPM2.0 is not impacted by this. We recommend updating your library to 0.3.0 or later, or, if you cannot update, to call CreateWrapKey with a random 20-byte value for 'migrationAuth'.
0
Attacker Value
Unknown
CVE-2020-14347
Disclosure Date: August 05, 2020 (last updated February 21, 2025)
A flaw was found in the way xserver memory was not properly initialized. This could leak parts of server memory to the X client. In cases where Xorg server runs with elevated privileges, this could result in possible ASLR bypass. Xorg-server before version 1.20.9 is vulnerable.
0
Attacker Value
Unknown
CVE-2020-1389
Disclosure Date: July 14, 2020 (last updated February 21, 2025)
An information disclosure vulnerability exists when the Windows kernel fails to properly initialize a memory address, aka 'Windows Kernel Information Disclosure Vulnerability'. This CVE ID is unique from CVE-2020-1367, CVE-2020-1419, CVE-2020-1426.
0
Attacker Value
Unknown
CVE-2020-4067
Disclosure Date: June 29, 2020 (last updated February 21, 2025)
In coturn before version 4.5.1.3, there is an issue whereby STUN/TURN response buffer is not initialized properly. There is a leak of information between different client connections. One client (an attacker) could use their connection to intelligently query coturn to get interesting bytes in the padding bytes from the connection of another client. This has been fixed in 4.5.1.3.
0
Attacker Value
Unknown
CVE-2020-0586
Disclosure Date: June 15, 2020 (last updated February 21, 2025)
Improper initialization in subsystem for Intel(R) SPS versions before SPS_E3_04.01.04.109.0 and SPS_E3_04.08.04.070.0 may allow an authenticated user to potentially enable escalation of privilege and/or denial of service via local access.
0
Attacker Value
Unknown
CVE-2020-0529
Disclosure Date: June 15, 2020 (last updated February 21, 2025)
Improper initialization in BIOS firmware for 8th, 9th and 10th Generation Intel(R) Core(TM) Processor families may allow an unauthenticated user to potentially enable escalation of privilege via local access.
0
Attacker Value
Unknown
CVE-2020-9833
Disclosure Date: June 09, 2020 (last updated February 21, 2025)
A memory initialization issue was addressed with improved memory handling. This issue is fixed in macOS Catalina 10.15.5. A local user may be able to read kernel memory.
0