CVE-2024-33850VulnerabilityPublished 10 Jun 2024Updated 21 Nov 2024

CVE-2024-33850: n/a

Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium · fixed in 34.1 : update affected systems when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 34.1

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-33850, organizations should promptly upgrade Pexip Infinity to version 34.1 or later where the vulnerability is addressed. In the absence of immediate patching, administrators should review and tighten waiting room configurations to restrict access and minimize exposure. This includes limiting network access to conferencing infrastructure, enforcing strict firewall rules, and monitoring waiting room activity for anomalous behavior. Employing network segmentation to isolate conferencing servers from general user networks can reduce attack surface. Additionally, organizations should implement strong authentication and authorization policies for conference admission, ensuring only trusted users can join meetings. Regularly auditing conference logs and participant lists can help detect unauthorized access attempts. Security teams should stay informed about updates from Pexip and apply vendor advisories promptly. Finally, educating users about the risks of waiting room vulnerabilities and encouraging vigilance can further reduce exploitation likelihood.

Description

Pexip Infinity before 34.1 has Improper Access Control for persons in a waiting room. They can see the conference roster list, and perform certain actions that should not be allowed before they are admitted to the meeting.

Impact

The impact of CVE-2024-33850 is primarily on confidentiality and integrity within video conferencing environments. Unauthorized waiting room users can view participant rosters, potentially exposing sensitive identities and meeting details. This information leakage could facilitate social engineering or targeted attacks. Additionally, the ability to perform certain unauthorized actions before admission could disrupt meeting flow or integrity, though the exact scope of these actions is unspecified. Availability impact is limited but possible if disruptive actions affect meeting stability. Organizations relying on Pexip Infinity for confidential communications, such as government agencies, healthcare providers, and enterprises with sensitive intellectual property, face increased risk of information exposure and meeting disruption. While the attack vector requires network or physical proximity, the lack of authentication or user interaction requirements lowers the barrier to exploitation within accessible environments. The absence of known exploits reduces immediate threat but does not eliminate risk, especially as attackers may develop exploits post-disclosure. Overall, the vulnerability could undermine trust in secure conferencing and lead to privacy violations or operational interruptions.

References

docs.pexip.com/admin/security_bulletins.htm (opens in a new tab)

Community reviews

Loading reviews…