dbcve.org
Advanced System CareApplication · Iobit

CVE-2022-24140

MEDIUM · 6.6 CVSS v3.1 Published 2022-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
IOBit Advanced System Care 15, iTop Screen Recorder 2.1, iTop VPN 3.2, Driver Booster 9, and iTop Screenshot sends HTTP requests in their update procedure in order to download a config file. After downloading the config file, the products will parse the HTTP location of the update from the file and will try to install the update automatically with ADMIN privileges. An attacker Intercepting this communication can supply the product a fake config file with malicious locations for the updates thus gaining a remote code execution on an endpoint.

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 confidence

Multiple IOBit products (Advanced System Care 15, iTop Screen Recorder 2.1, iTop VPN 3.2, Driver Booster 9, iTop Screenshot) use insecure HTTP connections to download update configuration files during their update procedure. An attacker performing a Man-in-the-Middle (MitM) attack can intercept these unencrypted requests and supply a malicious config file containing arbitrary update URLs, causing the software to download and execute code with administrator privileges.

MitigationEnforce HTTPS for all update communications with proper certificate validation, and implement cryptographic verification (digital signatures or checksums) of config files before parsing or executing any updates.

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
Advanced System CareApplication
Affected:= 15
Driver BoosterApplication
Affected:= 9
Itop Screen RecorderApplication
Affected:= 2.1
Itop ScreenshotApplication
Affected:all versions
Itop VpnApplication
Affected:= 3.2

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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IObit products
    Check Program Files or Program Files (x86) folders for IObit subdirectories (e.g., IObit, Advanced SystemCare, Driver Booster, iTop VPN, iTop Screen Recorder, iTop Screenshot). Also check Add/Remove Programs or registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for IObit entries.
    Affected if Any of these IObit products are present: Advanced SystemCare 15, Driver Booster 9, iTop Screen Recorder 2.1, iTop Screenshot (any version), or iTop VPN 3.2
  2. Inspect update configuration files
    Locate update-related config files within the product installation directories. Common paths include the main product folder or subfolders named Config, Update, or Settings. Look for files with .ini, .cfg, .xml, or .config extensions that may contain update server URLs.
    Affected if Configuration files contain HTTP URLs (not HTTPS) pointing to update or download servers
  3. Capture network traffic during update check
    Use a network sniffer (Wireshark), proxy (Fiddler), or Windows Event Viewer with network logging to observe outbound connections when running the update feature. Monitor for unencrypted HTTP requests to IObit update domains.
    Affected if The software makes unencrypted HTTP requests to retrieve update configuration or files
  4. Check update module registry entries
    Examine Windows registry keys related to the product update mechanism. Check under HKLM\SOFTWARE\IObit or within the specific product's registry folder for UpdateServer, UpdateURL, or ConfigURL entries.
    Affected if Registry values show HTTP URLs for update configuration retrieval

If any of the affected IObit products are installed and the update process uses unencrypted HTTP connections to fetch configuration files, the environment is vulnerable to CVE-2022-24140.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enforce HTTPS for all update communications with proper certificate validation, and implement cryptographic verification (digital signatures or checksums) of config files before parsing or executing any updates.

Fix this in Advanced System Care Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24140 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24140 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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