CVE-2022-23228
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 before 27.0 has improper WebRTC input validation. An unauthenticated remote attacker can use excessive resources, temporarily causing denial of service.
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 · high confidencePexip Infinity before version 27.0 contains improper WebRTC input validation that allows an unauthenticated remote attacker to send specially crafted WebRTC requests causing excessive resource consumption and temporary denial of service.
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>= 1.0, < 27.0CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 installed Pexip Infinity versionAccess the Pexip Infinity admin interface or check system information to determine the currently installed version number. Compare this against the affected range (versions before 27.0).Affected if Installed version is 1.0 or higher but below 27.0
-
Confirm WebRTC services are enabledLocate WebRTC-related configuration settings within the Pexip Infinity management portal or configuration files. Verify whether the WebRTC feature or service is actively enabled.Affected if WebRTC is enabled and running on the system
-
Determine if WebRTC is exposed to unauthenticated usersReview network configuration and firewall settings to check whether the WebRTC service port or endpoint is accessible to unauthenticated/external users without authentication requirements.Affected if WebRTC is accessible to unauthenticated remote users without authentication controls
-
Check for abnormal WebRTC connection patternsReview WebRTC access logs or network traffic logs for unusual patterns such as a high volume of incoming WebRTC connection requests from external sources, repeated connection attempts, or requests with unusual characteristics.Affected if Excessive or anomalous WebRTC connection attempts are observed from external sources
The environment is affected if Pexip Infinity version is below 27.0 AND WebRTC is enabled and exposed to unauthenticated external users.
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.0
Upgrade Pexip Infinity to version 27.0 or later to obtain the patched WebRTC input validation. If immediate upgrade is not possible, consider rate limiting or firewall rules to limit external WebRTC traffic as a temporary measure.
27.0
- Plan for an upgrade of Pexip Infinity to version 27.0 or later
- Review Pexip upgrade documentation at docs.pexip.com for version 27.0 upgrade procedures
- Execute the upgrade following standard Pexip deployment procedures
- After upgrade, verify WebRTC functionality is operational and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23228 — 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-23228 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