Cyber Resilience

CVE-2024-44730

Published
11 October 2024
Modified
15 April 2026
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0043 35th percentile
Risk Priority 67 floored blend · peak EPSS

Summary

CVE-2024-44730 is a critical-severity Improper Enforcement of Message Integrity During Transmission in a Communication Channel (CWE-924) vulnerability in Aware7 (inferred from references). Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Adversary-in-the-Middle (T1557); ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-8 (Transmission Confidentiality and Integrity) and SC-16 (Transmission of Security and Privacy Attributes) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-52288Shared CWE-924
CVE-2023-22372Shared CWE-924
CVE-2025-0592Shared CWE-924
CVE-2023-49933Shared CWE-924
CVE-2026-54891Shared CWE-924
CVE-2023-2885Shared CWE-924
CVE-2024-39229Shared CWE-924
CVE-2019-25719Shared CWE-924
CVE-2026-39827Shared CWE-924
CVE-2023-26979Shared CWE-924

Affected Assets

Aware7
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

Requires protection of integrity for transmitted information, directly stopping the failure to verify messages were unmodified in transit.

Associates integrity-related security attributes with exchanged information, helping ensure modification can be detected during transmission.

Protects session authenticity, which structurally reduces the ability to undetectably modify messages in the channel.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-02 full match
prevents

Directly requires integrity protection (e.g., signatures/hashes) for data-in-transit, which prevents the described weakness while also addressing confidentiality/availability.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Mandates network security controls that can enforce message integrity on channels.

prevents

Addresses security of network services, which may include integrity mechanisms.

prevents

Cryptography is the primary technical means to enforce message integrity during transmission.

prevents

Requires secure information transfer procedures that can include integrity checks.

prevents

Application security requirements can specify integrity protection for transmitted messages.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (4 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-924
  • V-248823 OL 8 must not have the telnet-server package installed. prevents CWE-924
  • V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-924

References