CVE-2022-25357
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPexip Infinity 27.x before 27.2 has Improper Access Control. An attacker can sometimes join a conference (call join) if it has a lock but not a PIN.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePexip Infinity versions before 27.2 contain an improper access control vulnerability where an attacker can bypass conference locking. Specifically, when a conference is configured with a lock but without a PIN, the lock protection can be circumvented, allowing unauthorized participants to join the call.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 27.0, < 27.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Pexip Infinity versionAccess the Pexip Infinity admin interface and navigate to 'Platform' > 'About' or use the command line 'version' command on the management node to retrieve the deployed software version.Affected if The installed version is 27.0, 27.1, or any version >= 27.0 but < 27.2.
-
Review conference lock configurationsIn the Pexip Infinity admin interface, go to 'Conferences' and examine the conference configurations. Look for conferences that have 'Lock conference' enabled.Affected if Any conference is configured with the lock option enabled.
-
Check for PIN requirements on locked conferencesFor each conference with lock enabled, verify whether a PIN (personal identification number) is required to join. This setting is typically found in the conference security or access settings within the admin interface.Affected if A conference is locked but does not require a PIN (PIN is set to optional or disabled).
A user is affected if they are running Pexip Infinity version 27.0 through 27.1 and have any conferences configured with locking enabled but without a mandatory PIN requirement.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped27.2
Upgrade Pexip Infinity to version 27.2 or later to remediate the access control bypass. Review conference configurations to ensure appropriate locking and PIN settings are in place.
Pexip Infinity 27.2 or later
- 1. Identify the current Pexip Infinity version by accessing the admin interface or checking system information
- 2. Plan for a maintenance window and backup the current configuration
- 3. Obtain the Pexip Infinity 27.2 or later upgrade package from the official Pexip download portal
- 4. Follow the standard Pexip upgrade procedure documented at docs.pexip.com for your deployment type
- 5. After upgrade, verify the version shows 27.2 or higher in the admin interface
- 6. Test that the conference locking functionality now properly restricts access when a lock is enabled without a PIN
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-25357 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data