Service interruption via H.264 resource exhaustion
Published Jul 17, 2022 · Updated Aug 3, 2024
Resource exhaustion in Pexip Infinity before 27.3 allows remote attackers to interrupt conferencing service through H.264 media. Processing attacker-controlled H.264 media consumes excessive resources; Pexip has not disclosed the affected parser or operation. Network access without authentication is sufficient, and the documented consequence is limited to service interruption.
Summary
What happened
Resource exhaustion in Pexip Infinity before 27.3 allows remote attackers to interrupt conferencing service through H.264 media. Processing attacker-controlled H.264 media consumes excessive resources; Pexip has not disclosed the affected parser or operation. Network access without authentication is sufficient, and the documented consequence is limited to service interruption.
The record
- CVE
- CVE-2022-27937
- Published
- Jul 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 17, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo