CVE-2024-6080
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability classified as critical was found in Intelbras InControl 2.21.56. This vulnerability affects unknown code of the component incontrolWebcam Service. The manipulation leads to unquoted search path. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. Upgrading to version 2.21.58 is able to address this issue. It is recommended to upgrade the affected component. The vendor was contacted early about this disclosure and plans to provide a solution within the next few weeks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn unquoted search path vulnerability exists in the incontrolWebcam Service component of Intelbras InControl version 2.21.56. This allows a local attacker to place a malicious executable in an intermediate directory within the service's path, potentially achieving arbitrary code execution with elevated privileges when the service starts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.21.56CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Intelbras InControl installation and versionCheck the installed version of Intelbras InControl by reviewing the program's version information in Control Panel > Programs and Features, or by locating the InControl executable and viewing its file properties.Affected if The installed version is exactly 2.21.56.
-
Locate the incontrolWebcam serviceOpen Services console (services.msc) or run 'sc query incontrolWebcam' from an elevated command prompt to find the service.Affected if The incontrolWebcam service exists on the system.
-
Examine the service binary path for unquoted spacesRun 'sc qc incontrolWebcam' from an elevated command prompt and inspect the BINARY_PATH_NAME field. Look for paths containing spaces that are not enclosed in quotation marks.Affected if The service binary path contains spaces but is not wrapped in quotation marks.
-
Check for suspicious executables in intermediate path directoriesIf the service path has unquoted spaces, examine each directory in the path (the folders between the drive letter and the executable name) for any unexpected or malicious .exe files placed there.Affected if Unexpected executable files exist in any intermediate directory along the service's unquoted path.
A system is affected if Intelbras InControl version 2.21.56 is installed and the incontrolWebcam service has a binary path with unquoted spaces that could be exploited for privilege escalation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Intelbras InControl to version 2.21.58 or later to address this vulnerability.
InControl version 2.21.58
- 1. Backup the current Intelbras InControl installation and any associated data before proceeding with the upgrade
- 2. Download InControl version 2.21.58 from the official Intelbras vendor sources (backend.intelbras.com or download.cronos.intelbras.com.br)
- 3. Uninstall or upgrade the existing InControl 2.21.56 installation
- 4. Install the InControl 2.21.58 version
- 5. Verify the incontrolWebcam Service is running correctly and the application functions normally
- 6. Confirm the unquoted search path vulnerability is resolved by verifying the service executable path is properly quoted or updated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6080 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6080 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data