CVE-2023-50923: CSRF
In QUIC in RFC 9000, the Latency Spin Bit specification (section 17.4) does not strictly constrain the bit value when the feature is disabled, which might allow remote attackers to construct a covert channel with data represented as changes to the bit value. NOTE: The "Sheridan, S., Keane, A. (2015). In Proceedings of the 14th European Conference on Cyber Warfare and Security (ECCWS), University of Hertfordshire, Hatfield, UK." paper says "Modern Internet communication protocols provide an almost infinite number of ways in which data can be hidden or embed whithin seemingly normal network traffic."
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-50923?
CVE-2023-50923 is considered a medium severity vulnerability due to its potential to enable covert communication channels.
How do I fix CVE-2023-50923?
Currently, there are no official fixes for CVE-2023-50923, but monitoring and restricting the use of the Latency Spin Bit feature may help mitigate risk.
Who is affected by CVE-2023-50923?
CVE-2023-50923 affects implementations of the IETF QUIC (RFC 9000) protocol that utilize the Latency Spin Bit feature.
What impact does CVE-2023-50923 have on network security?
CVE-2023-50923 may allow remote attackers to create covert channels for unauthorized data transmission, potentially compromising network security.
What does the Latency Spin Bit refer to in the context of CVE-2023-50923?
The Latency Spin Bit is a feature in the QUIC protocol meant to indicate changes in latency, but its lack of strict constraints when disabled poses a security risk in CVE-2023-50923.