Show filters
2,446 Total Results
Displaying 91-100 of 2,446
Sort by:
Attacker Value
Unknown
CVE-2020-25719
Disclosure Date: February 18, 2022 (last updated February 23, 2025)
A flaw was found in the way Samba, as an Active Directory Domain Controller, implemented Kerberos name-based authentication. The Samba AD DC, could become confused about the user a ticket represents if it did not strictly require a Kerberos PAC and always use the SIDs found within. The result could include total domain compromise.
0
Attacker Value
Unknown
CVE-2020-25717
Disclosure Date: February 18, 2022 (last updated February 23, 2025)
A flaw was found in the way Samba maps domain users to local users. An authenticated attacker could use this flaw to cause possible privilege escalation.
0
Attacker Value
Unknown
CVE-2016-2124
Disclosure Date: February 18, 2022 (last updated February 23, 2025)
A flaw was found in the way samba implemented SMB1 authentication. An attacker could use this flaw to retrieve the plaintext password sent over the wire even if Kerberos authentication was required.
0
Attacker Value
Unknown
CVE-2021-38665
Disclosure Date: November 10, 2021 (last updated November 28, 2024)
Remote Desktop Protocol Client Information Disclosure Vulnerability
0
Attacker Value
Unknown
CVE-2021-34535
Disclosure Date: August 12, 2021 (last updated November 28, 2024)
Remote Desktop Client Remote Code Execution Vulnerability
0
Attacker Value
Unknown
CVE-2021-33037
Disclosure Date: July 12, 2021 (last updated February 23, 2025)
Apache Tomcat 10.0.0-M1 to 10.0.6, 9.0.0.M1 to 9.0.46 and 8.5.0 to 8.5.66 did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when used with a reverse proxy. Specifically: - Tomcat incorrectly ignored the transfer encoding header if the client declared it would only accept an HTTP/1.0 response; - Tomcat honoured the identify encoding; and - Tomcat did not ensure that, if present, the chunked encoding was the final encoding.
0
Attacker Value
Unknown
CVE-2021-1536
Disclosure Date: June 02, 2021 (last updated February 22, 2025)
A vulnerability in Cisco Webex Meetings Desktop App for Windows, Cisco Webex Meetings Server, Cisco Webex Network Recording Player for Windows, and Cisco Webex Teams for Windows could allow an authenticated, local attacker to perform a DLL injection attack on an affected device. To exploit this vulnerability, the attacker must have valid credentials on the Windows system. This vulnerability is due to incorrect handling of directory paths at run time. An attacker could exploit this vulnerability by inserting a configuration file in a specific path in the system, which can cause a malicious DLL file to be loaded when the application starts. A successful exploit could allow the attacker to execute arbitrary code on the affected system with the privileges of another user account.
0
Attacker Value
Unknown
CVE-2021-1502
Disclosure Date: June 02, 2021 (last updated February 22, 2025)
A vulnerability in Cisco Webex Network Recording Player for Windows and MacOS and Cisco Webex Player for Windows and MacOS could allow an attacker to execute arbitrary code on an affected system. The vulnerability is due to insufficient validation of values within Webex recording files formatted as either Advanced Recording Format (ARF) or Webex Recording Format (WRF). An attacker could exploit the vulnerability by sending a user a malicious ARF or WRF file through a link or email attachment and persuading the user to open the file. A successful exploit could allow the attacker to execute arbitrary code on the affected system with the privileges of the targeted user.
0
Attacker Value
Unknown
CVE-2018-10195
Disclosure Date: June 02, 2021 (last updated February 22, 2025)
lrzsz before version 0.12.21~rc can leak information to the receiving side due to an incorrect length check in the function zsdata that causes a size_t to wrap around.
0
Attacker Value
Unknown
CVE-2021-3450
Disclosure Date: March 25, 2021 (last updated February 22, 2025)
The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named "purpose" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verific…
0