CVE-2020-1887
Incorrect validation of the TLS SNI hostname in osquery versions after 2.9.0 and before 4.2.0 could allow an attacker to MITM osquery traffic in the absence of a configured root chain of trust.
Incorrect validation of the TLS SNI hostname in osquery versions after 2.9.0 and before 4.2.0 could allow an attacker to MITM osquery traffic in the absence of a configured root chain of trust.
Incorrect validation of the TLS SNI hostname in osquery versions after 2.9.0 and before 4.2.0 could allow an attacker to MITM osquery traffic in the absence of a configured root chain of trust.
In the GlobalBlocking extension before 2020-03-10 for MediaWiki through 1.34.0, an issue related to IP range evaluation resulted in blocked users re-gaining escalated privileges. This is related to the case in which an IP address is contained in two ranges, one of which is locally disabled.
In the GlobalBlocking extension before 2020-03-10 for MediaWiki through 1.34.0, an issue related to IP range evaluation resulted in blocked users re-gaining escalated privileges. This is related to the case in which an IP address is contained in two ranges, one of which is locally disabled.
In the GlobalBlocking extension before 2020-03-10 for MediaWiki through 1.34.0, an issue related to IP range evaluation resulted in blocked users re-gaining escalated privileges. This is related to the case in which an IP address is contained in two ranges, one of which is locally disabled.
In the GlobalBlocking extension before 2020-03-10 for MediaWiki through 1.34.0, an issue related to IP range evaluation resulted in blocked users re-gaining escalated privileges. This is related to the case in which an IP address is contained in two ranges, one of which is locally disabled.
This all started with a simple request. A client had purchased some new, shiny networking gear, and in each failover pair the active unit was sending 1 “Runt” per second. A “runt” is a frame that is smaller than the legal minimum, in other words, 64 bytes. I guess it doesn’t qualify as a packet, …
This all started with a simple request. A client had purchased some new, shiny networking gear, and in each failover pair the active unit was sending 1 “Runt” per second. A “runt” is a frame that is smaller than the legal minimum, in other words, 64 bytes. I guess it doesn’t qualify as a packet, …
This all started with a simple request. A client had purchased some new, shiny networking gear, and in each failover pair the active unit was sending 1 “Runt” per second. A “runt” is a frame that is smaller than the legal minimum, in other words, 64 bytes. I guess it doesn’t qualify as a packet, …
This all started with a simple request. A client had purchased some new, shiny networking gear, and in each failover pair the active unit was sending 1 “Runt” per second. A “runt” is a frame that is smaller than the legal minimum, in other words, 64 bytes. I guess it doesn’t qualify as a packet, …