CVE-2021-32545
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 26 allows remote denial of service because of missing RTMP input validation.
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 video conferencing platform before version 26 is vulnerable to remote denial of service due to missing validation of RTMP (Real-Time Messaging Protocol) input. Attackers can send specially crafted RTMP requests to trigger the DoS condition without authentication.
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< 26CVSS 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.
-
Check Pexip Infinity versionLocate the Pexip Infinity management interface or check the installed software version through the admin console or system information. Typical locations include the admin web UI or CLI: `show system information` or similar version command.Affected if The installed version is any release before version 26 (e.g., 25.x, 24.x, etc.)
-
Verify RTMP service statusAccess the Pexip Infinity admin interface and check whether RTMP inbound or outbound functionality is enabled. This is typically found under Conferencing > RTMP settings or similar configuration section.Affected if RTMP functionality is enabled or configured on the system
-
Review RTMP-related logsExamine Pexip Infinity logs for any RTMP connection errors, unexpected disconnects, or crash events. Check logs under Diagnostics > View logs or the system log directory.Affected if There are recent RTMP connection failures, service disruptions, or error messages related to RTMP input processing
-
Check network exposure of RTMP portIdentify if RTMP ports (default TCP 1935 and any configured RTMP listener ports) are exposed to untrusted networks. Review firewall rules or port configurations.Affected if RTMP services are reachable from external or untrusted network segments without proper access controls
A system is affected if it runs any Pexip Infinity version before 26 with RTMP functionality enabled and exposed, as the missing RTMP input validation can be exploited by unauthenticated attackers to cause denial of service.
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 · scoped26
Upgrade Pexip Infinity to version 26 or later to obtain the RTMP input validation fixes.
Infinity version 26
- Review Pexip Infinity upgrade documentation at docs.pexip.com for version 26 upgrade procedures
- Plan the upgrade during a scheduled maintenance window
- Back up the current Infinity configuration and database
- Upgrade Pexip Infinity to version 26 or later to address the RTMP input validation vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32545 — 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-2021-32545 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