CVE-2024-9325
LPE in Intelbras Incontrol Web ≤ 2.21.58
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2024-9325 is a high-severity Untrusted Search Path (CWE-426) vulnerability in Intelbras Incontrol Web. Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 26th 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 CM-6 (Configuration Settings) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-49864
Vulnerability Data
A vulnerability classified as critical has been found in Intelbras InControl up to 2.21.56. This affects an unknown part of the file C:\Program Files (x86)\Intelbras\Incontrol Cliente\incontrol_webcam\incontrol-service-watchdog.exe. The manipulation leads to unquoted search path. It is possible to launch the attack…
more
on the local host. Upgrading to version 2.21.58 is able to address this issue. It is recommended to upgrade the affected component. The vendor was informed early on 2024-08-05 about this issue. The release of a fixed version 2.21.58 was announced for the end of August 2024 but then was postponed until 2024-09-20.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Secure baseline settings can enforce absolute, organization-controlled paths for critical resources.
Developer testing and evaluation can discover unquoted search paths through static analysis or dynamic test cases.
Least-functionality configuration can prohibit unapproved directories or executables from being reachable via search paths.
Documented development standards and tools can mandate proper quoting and escaping of path elements.
Engineering principles such as trusted paths, complete mediation, and least privilege directly require hard-coded or validated search paths instead of external ones.
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.
Preventing execution of unauthorized code directly blocks the malicious binaries that an untrusted search path would load.
Secure development practices include avoiding or sanitizing externally influenced search paths in application code.
Hardened configuration baselines can enforce safe search paths and restrict environment variables that enable the weakness.
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 can discover search-path issues but does not itself prevent them in production code.
Restricting software installation reduces the chance that untrusted binaries or libraries are placed in search paths.
Secure development lifecycle practices include input validation and path handling that reduce unquoted search-path weaknesses.
Secure architecture principles include hard-coded or validated search paths and avoiding reliance on untrusted directories.
Secure coding standards require absolute paths or integrity-checked search paths, directly mitigating CWE-426.
Change-management processes can enforce review of path-handling changes that might introduce unquoted elements.