CVE-2023-22854
Mitel Micontact Center Business 9.2.2.0 – 9.4.2.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-22854 is a high-severity Numeric Range Comparison Without Minimum Check (CWE-839) vulnerability in Mitel Micontact Center Business. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique LSASS Memory (T1003.001); ranked at the 47th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-26964
Vulnerability Data
The ccmweb component of Mitel MiContact Center Business server 9.2.2.0 through 9.4.1.0 could allow an unauthenticated attacker to download arbitrary files, due to insufficient restriction of URL parameters. A successful exploit could allow access to sensitive information.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 1 OS baseline
—
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.
Secure SDLC practices directly require proper input validation and range checks that prevent missing minimum bounds.
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.
Secure development life cycle mandates input validation and boundary checks that would catch missing minimum-range verification.
A.8.26 only requires that security requirements (including resilience against injections or input validation) be identified and specified during development or acquisition; it does not itself enforce, implement or assure any check that stops a missing lower-bound comparison from being exploitable.
A.8.27 mandates establishing and applying secure engineering principles (including least privilege, security by design, and design reviews) but does not itself implement range checks or stop a missing-minimum numeric comparison from being coded and exploited
Secure coding standards explicitly forbid numeric comparisons that omit the lower bound, directly mitigating CWE-839.
Security testing in development and acceptance can detect missing minimum checks through boundary-value and fuzz testing.