Chat impersonation via unvalidated sender names
Published Oct 11, 2024 · Updated Oct 16, 2024
Incorrect access control in MiroTalk P2P before commit c21d58 allows remote attackers to forge chat messages under arbitrary sender names. handleDataChannelChat trusts the sender name carried by an incoming data-channel message instead of binding it to the sending peer. Network access to a meeting data channel is sufficient, and the bounded consequence is participant impersonation within chat rather than server code execution.
Summary
What happened
Incorrect access control in MiroTalk P2P before commit c21d58 allows remote attackers to forge chat messages under arbitrary sender names. handleDataChannelChat trusts the sender name carried by an incoming data-channel message instead of binding it to the sending peer. Network access to a meeting data channel is sufficient, and the bounded consequence is participant impersonation within chat rather than server code execution.
The record
- CVE
- CVE-2024-44730
- Published
- Oct 11, 2024
- Updated
- Oct 16, 2024
- Vendor
- MiroTalk
- Product
- MiroTalk P2P
- Classifications
- CWE-924, T1656
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2024CVE publishedPublication date reported by the CVE source.
- Oct 16, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <c21d58
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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