Pexip Infinity vulnerabilities

Pexip Infinity before version 8 uses the same SSH host keys across different customers' installations, allowing man-in-the-middle attackers to spoof Management and Conferencing Nodes.

Pexip Infinity before 38.2, plus 39.0, 39.1 and 40.0, is affected by improper input validation that allows a remote attacker to execute code remotely as an unprivileged user on a Pexip Infinity Conferencing Node.

Pexip Infinity before version 14.2 allows remote attackers to cause a denial of service (service restart) or execute arbitrary code via vectors related to Conferencing Nodes.

Pexip Infinity before 38.2, plus 39.0, 39.1 and 40.0, is affected by improper input validation in the media implementation that allows a remote attacker to trigger memory corruption or a software abort resulting in a denial of service. A crafted media stream may result in a controlled abort during processing and has the potential to achieve memory corruption.

Pexip Infinity before 38.2, plus 39.0, 39.1, and 40.0, is affected by improper input validation in the media implementation that allows a remote attacker to trigger a software abort resulting in a denial of service.

Pexip Infinity before 38.2, plus 39.0, 39.1, and 40.0, is affected by improper input validation within an internal Pexip Infinity service that allows an attacker with local access to escalate privileges to root. Exploitation requires the attacker to be able to run arbitrary code on a node, either by achieving remote code execution via another vulnerability or by having administrative access to the operating system.

Pexip Infinity before 38.2, plus 39.0, 39.1 and 40.0, is affected by improper access control on a product-internal API which allows an attacker with local access to a node within a Pexip Infinity installation to execute arbitrary code as an unprivileged user on another Pexip Infinity node.

Pexip Infinity before 38.2, plus 39.0, 39.1 and 40.0, is affected by improper input validation in the media implementation which allows a remote attacker to trigger a software abort resulting in a denial of service.

Pexip Infinity before 41.0 is affected by improper input validation in the signaling implementation which allows a remote attacker to trigger a software abort resulting in a denial of service. Exploitation of this issue requires accessing a gateway call from a WebRTC/API client.

Pexip Infinity 30.0 through 40.x before 41.0 is affected by improper input validation in the web server that allows a malicious attacker to render a Pexip Infinity node inaccessible.

Pexip Infinity before 40.1 is affected by improper input validation in the signaling implementation that allows a malicious attacker to trigger a software abort resulting in a denial of service.

Pexip Infinity before 41.1 is affected by improper input validation in the media implementation that allows a remote attacker to trigger a software abort resulting in a denial of service.

Pexip Infinity versions 35.0 through 38.1 before 39.0, in non-default configurations using Direct Media for WebRTC, has improper input validation in signalling that allows an attacker to trigger a software abort, resulting in a temporary denial of service.

Pexip Infinity before version 39.0 has improper input validation in the media implementation. A remote attacker can trigger a software abort via a crafted media stream, resulting in a denial of service.

Insufficient access control in the RTMP implementation in Pexip Infinity through 38.1 allows an attacker to disconnect RTMP streams traversing a Proxy Node.

Pexip Infinity before 39.0 has Missing Authentication for a Critical Function in a product-internal API, allowing an attacker (who already has access to execute code on one node within a Pexip Infinity installation) to impact the operation of other nodes within the installation.

Vulnerability in Pexip Infinity versions 15.0 through 38.0 before 38.1 involves improper access control in the Secure Scheduler for Exchange service when used with Office 365 Legacy Exchange Tokens. A remote attacker can read potentially sensitive data and excessively consume resources, leading to denial of service.

Pexip Infinity versions 32.0 through 37.1 before 37.2, in certain OTJ (One Touch Join) configurations for Teams SIP Guest Join, has Improper Input Validation in the OTJ service, allowing a remote attacker to trigger a software abort via a crafted calendar invite, leading to a denial of service.

Pexip Infinity versions 35.0 through 37.2 before 38.0 has improper input validation in signalling that allows an attacker to trigger a software abort, resulting in a denial of service.

Pexip Infinity versions 33.0 through 37.0 before 37.1 have improper input validation in signaling that allows an attacker to trigger a software abort, resulting in a denial of service.

Pexip Infinity before 37.0 has improper input validation in signalling that allows a remote attacker to trigger a software abort via a crafted signalling message, resulting in a denial of service.