CVE-2024-44730VulnerabilityPublished 11 Oct 2024Updated 16 Oct 2024

CVE-2024-44730: n/a

Source CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Until an official patch is released, organizations should implement several practical mitigations: 1) Restrict access to Mirotalk instances to trusted networks or VPNs to reduce exposure to unauthenticated attackers. 2) Implement network-level controls such as firewall rules or WebRTC signaling restrictions to limit data channel connections to authenticated users. 3) Monitor chat logs and audit trails for unusual message patterns or sender anomalies that could indicate message forgery. 4) Consider deploying additional application-layer verification mechanisms, such as cryptographic message signing or sender identity validation, to detect and reject forged messages. 5) Educate users to be cautious about unexpected or suspicious chat messages, especially those requesting sensitive information or actions. 6) Follow Mirotalk project updates closely and apply patches immediately once available. 7) If feasible, isolate Mirotalk deployments from critical systems to minimize potential lateral movement or data leakage. These steps go beyond generic advice by focusing on network segmentation, monitoring, and layered verification to mitigate the risk in the absence of a patch.

Description

Incorrect access control in the function handleDataChannelChat(dataMessage) of Mirotalk before commit c21d58 allows attackers to forge chat messages using an arbitrary sender name.

Impact

The primary impact of CVE-2024-44730 is on the confidentiality and integrity of communications within Mirotalk deployments. Attackers can impersonate legitimate users by forging chat messages, which can lead to misinformation dissemination, manipulation of conversations, and social engineering attacks targeting users or organizations. This can erode trust in communication channels, cause reputational damage, and potentially facilitate further attacks such as phishing or insider threat exploitation. Since Mirotalk is used for real-time collaboration, the ability to spoof messages undermines the reliability of the platform. Although availability is not directly impacted, the indirect consequences of misinformation or compromised trust can disrupt organizational workflows. The vulnerability is exploitable remotely without authentication or user interaction, increasing the risk of widespread exploitation once a public exploit emerges. Organizations relying on Mirotalk for sensitive or critical communications are particularly vulnerable, especially those in sectors like government, finance, healthcare, and education where secure communications are paramount.

CWE-924Improper Enforcement of Message Integrity During Transmission in a Communication Channel (opens in a new tab)
Base weakness
The product establishes a communication channel with an endpoint and receives a message from that endpoint, but it does not sufficiently ensure that the message was not modified during transmission.
OWASP Cheat Sheets
XML Security (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
REST Assessment (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.2 (opens in a new tab)
V3.5.3 (opens in a new tab)
V13.2.6 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 07:59 UTC

WeaknessesCWE-924

Technical details

References

Community reviews

Related threats