Show filters
6 Total Results
Displaying 1-6 of 6
Sort by:
Attacker Value
Unknown
CVE-2020-36406
Disclosure Date: July 01, 2021 (last updated November 08, 2023)
uWebSockets 18.11.0 and 18.12.0 has a stack-based buffer overflow in uWS::TopicTree::trimTree (called from uWS::TopicTree::unsubscribeAll). NOTE: the vendor's position is that this is "a minor issue or not even an issue at all" because the developer of an application (that uses uWebSockets) should not be allowing the large number of triggered topics to accumulate
0
Attacker Value
Unknown
CVE-2021-33880
Disclosure Date: June 06, 2021 (last updated November 28, 2024)
The aaugustin websockets library before 9.1 for Python has an Observable Timing Discrepancy on servers when HTTP Basic Authentication is enabled with basic_auth_protocol_factory(credentials=...). An attacker may be able to guess a password via a timing attack.
0
Attacker Value
Unknown
CVE-2018-1000518
Disclosure Date: June 26, 2018 (last updated November 26, 2024)
aaugustin websockets version 4 contains a CWE-409: Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in Servers and clients, unless configured with compression=None that can result in Denial of Service by memory exhaustion. This attack appear to be exploitable via Sending a specially crafted frame on an established connection. This vulnerability appears to have been fixed in 5.
0
Attacker Value
Unknown
CVE-2017-0249
Disclosure Date: May 12, 2017 (last updated November 26, 2024)
An elevation of privilege vulnerability exists when the ASP.NET Core fails to properly sanitize web requests.
0
Attacker Value
Unknown
CVE-2017-0256
Disclosure Date: May 12, 2017 (last updated November 26, 2024)
A spoofing vulnerability exists when the ASP.NET Core fails to properly sanitize web requests.
0
Attacker Value
Unknown
CVE-2017-0247
Disclosure Date: May 12, 2017 (last updated November 26, 2024)
A denial of service vulnerability exists when the ASP.NET Core fails to properly validate web requests. NOTE: Microsoft has not commented on third-party claims that the issue is that the TextEncoder.EncodeCore function in the System.Text.Encodings.Web package in ASP.NET Core Mvc before 1.0.4 and 1.1.x before 1.1.3 allows remote attackers to cause a denial of service by leveraging failure to properly calculate the length of 4-byte characters in the Unicode Non-Character range.
0