CVE-2021-47790
BaseFortify
Publication date: 2026-01-16
Last updated on: 2026-01-16
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| py_software | active_webcam | 11.5 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-428 | The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an unquoted service path issue in Active WebCam version 11.5. Because the service path to the executable contains spaces but is not enclosed in quotes, a local attacker can place a malicious executable in a directory path that Windows might execute instead of the legitimate program. This allows the attacker to run arbitrary code with elevated system privileges, effectively escalating their privileges on the system. [1, 3]
How can this vulnerability impact me? :
The vulnerability can allow a local attacker to execute arbitrary code with administrative privileges on the affected system. This means the attacker can gain full control over the system, potentially leading to unauthorized access, data theft, system manipulation, or disruption of services. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking the service configuration for the Active WebCam service named "ACTIVEWEBCAM" to see if its binary path is unquoted and contains spaces. Use the command "sc qc ACTIVEWEBCAM" to query the service configuration. Additionally, you can use Windows Management Instrumentation Command-line (WMIC) queries to verify the unquoted path. If the path is unquoted, it indicates the presence of the vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include correcting the service path by quoting the executable path in the service configuration to prevent Windows from executing malicious executables placed in unintended directories. Also, ensure that the "Start on Windows Startup" and "Start as Service" options are configured securely or disabled if not necessary. Applying the latest patches or updates from the software vendor, if available, is recommended to fix the unquoted service path vulnerability. [1, 3]