CVE-2024-52883
Path Traversal in Audiocodes One Voice Operations Center ≤ 8.4.582
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2024-52883 is a high-severity Path Traversal (CWE-22) vulnerability in Audiocodes One Voice Operations Center. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-52883 is a path traversal vulnerability (CWE-22) affecting AudioCodes One Voice Operations Center (OVOC) versions before 8.4.582. The flaw enables unauthenticated access to sensitive data through improper handling of file paths in requests. It carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), reflecting high confidentiality impact, network accessibility, low attack complexity, and no requirements for privileges or user interaction.
An unauthenticated attacker with network access to an affected OVOC instance can exploit this vulnerability by crafting requests that manipulate directory traversal sequences, such as using "../" patterns, to read arbitrary sensitive files on the server. Successful exploitation results in unauthorized disclosure of confidential information, potentially including configuration data, logs, or other proprietary files, without impacting integrity or availability.
Advisories provide further details on the issue, including SYSS-2024-075 available at https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2024-075.txt and the AudioCodes OVOC product page at https://www.audiocodes.com/solutions-products/products/management-products-solutions/one-voice-operations-center. The vulnerability was published on 2025-02-07, and upgrading to OVOC 8.4.582 or later addresses the path traversal flaw.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-5051
Vulnerability Data
An issue was discovered in AudioCodes One Voice Operations Center (OVOC) before 8.4.582. Due to a path traversal vulnerability, sensitive data can be read without any authentication.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
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.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
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.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.