CVE-2022-50935
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 · uneditedFlame II HSPA USB Modem contains an unquoted service path vulnerability in its Windows service configuration. Attackers can exploit the unquoted path in 'C:\Program Files (x86)\Internet Telcel\ApplicationController.exe' to execute arbitrary code with elevated system privileges.
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 confidenceThe Flame II HSPA USB Modem Windows service uses an unquoted executable path containing spaces (C:\Program Files (x86)\Internet Telcel\ApplicationController.exe). An attacker can place a malicious executable in an intermediate directory (e.g., 'C:\Program.exe' or 'C:\Program Files (x86)\Internet.exe') which Windows will execute before the intended binary due to the unquoted path, achieving code execution with SYSTEM privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 if ApplicationController service existsRun 'sc query ApplicationController' in Command Prompt or 'Get-Service -Name ApplicationController' in PowerShellAffected if The service is present on the system
-
Check the service binary path configurationRun 'sc qc ApplicationController' to view the service configuration, specifically the BINARY_PATH_NAME fieldAffected if The BINARY_PATH_NAME contains spaces and is not enclosed in quotation marks (e.g., shows C:\Program Files (x86)\Internet Telcel\ApplicationController.exe without quotes)
-
Identify intermediate directories in the unquoted pathParse the unquoted path to identify potential injection points: C:\Program.exe, C:\Program Files (x86)\Internet.exeAffected if The service path contains unquoted spaces creating intermediate directory opportunities
-
Check for malicious executables in intermediate directoriesInspect the file system for executables at: C:\Program.exe, C:\Program Files (x86)\Internet.exeAffected if Any unexpected executable exists in these intermediate path locations
-
Verify service logon accountRun 'sc qc ApplicationController' and check the START_TYPE and OBJECT_NAME fields, or use 'wmic service where name="ApplicationController" get StartName,State'Affected if The service runs as LocalSystem or another privileged account (OBJECT_NAME shows LocalSystem)
A system is affected if the ApplicationController service exists with an unquoted path containing spaces (C:\Program Files (x86)\Internet Telcel\ApplicationController.exe) and runs with elevated privileges, allowing potential code injection via intermediate directories.
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 · scopedThis vulnerability requires a vendor firmware/software update to properly quote the service path; the device is likely end-of-life. As a workaround, disable or remove the ApplicationController service if possible, and ensure strict file system permissions prevent unauthorized writes to parent directories.
- Open Windows Registry Editor (regedit.exe) and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ApplicationController
- Locate the 'ImagePath' value for the service
- Modify the ImagePath value to include quotes around the full path: "C:\Program Files (x86)\Internet Telcel\ApplicationController.exe"
- Close the registry editor
- Open Command Prompt as Administrator and verify the service configuration by running: sc qc ApplicationController
- Restart the Windows machine for changes to take full effect
- Alternatively, if the service is not essential, delete the service using: sc delete ApplicationController (requires reboot)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-50935 — 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-2022-50935 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