CVE-2024-35371: ant-media-server · n/a
Affects ant-media-serverSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% 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:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Nov 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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubant-media/ant-media-serverpkg:github/ant-media/ant-media-serverOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official patch is released, organizations should implement several specific mitigations: 1) Restrict access to log files strictly to trusted administrators and systems to minimize exposure of sensitive logged data. 2) Implement network-level controls such as firewalls and segmentation to limit exposure of Ant Media Server instances to untrusted networks. 3) Employ input validation and sanitization at the application or proxy level where possible to filter or neutralize potentially malicious or sensitive data before it reaches the logging mechanism. 4) Monitor logs for unusual or suspicious entries that may indicate exploitation attempts or injection of malicious content. 5) Consider disabling or reducing logging verbosity temporarily if feasible, to limit sensitive data capture. 6) Prepare for rapid deployment of official patches by maintaining up-to-date asset inventories and patch management processes. 7) Conduct security awareness training for administrators on the risks of log exposure and best practices for secure log management. These targeted actions go beyond generic advice by focusing on controlling log data exposure and proactively filtering inputs.
Description
Ant-Media-Serverv2.8.2 is affected by Improper Output Neutralization for Logs. The vulnerability stems from insufficient input sanitization in the logging mechanism. Without proper filtering or validation, user-controllable data, such as identifiers or other sensitive information, can be included in log entries without restrictions.
References
- github.com/ant-media/ant-media-server/commit/4d4763bd4fd06e515c19544e5170ca0f34c9ce45 (opens in a new tab)
- github.com/ant-media/Ant-Media-Server/blob/ams-v2.8.2/src/main/java/io/antmedia/rest/RestServiceBase.java (opens in a new tab)
- gist.github.com/1047524396/4eb17867f2e375f4824274c5e7b4d384 (opens in a new tab)