CVE-2021-44750
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 · uneditedAn arbitrary code execution vulnerability was found in the F-Secure Support Tool. A standard user can craft a special configuration file, which when run by administrator can execute any commands.
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 · moderate confidenceThe F-Secure Support Tool contains an arbitrary code execution vulnerability where a standard (non-privileged) user can craft a malicious configuration file. When an administrator subsequently runs the Support Tool, it parses and executes arbitrary commands embedded in this configuration file, resulting in privilege escalation to administrator-level code execution.
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 dataall versionsall versionsall versionsall versionsall versionsCVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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.
-
Confirm F-Secure Support Tool installationCheck for the presence of the F-Secure Support Tool executable or application on the system using standard software inventory or file system searchAffected if The Support Tool is installed on the system
-
Locate configuration directories used by Support ToolIdentify the configuration directory or directories that the F-Secure Support Tool reads from during execution. This may require reviewing installation documentation or monitoring file access during tool executionAffected if Configuration directories exist and are accessible
-
Check file ownership and permissions on configuration directoriesUse file system tools (such as icacls on Windows or ls -la on Linux) to examine the permissions on the identified configuration directoriesAffected if Standard (non-privileged) users have write permissions to directories containing configuration files used by privileged tools
-
Verify configuration file integrityExamine configuration files in the identified directories for any unexpected content, scripts, or commands that were not authored by administratorsAffected if Configuration files contain unexpected or malicious-looking commands or script entries
-
Review user group memberships on configuration filesCheck which user groups have modify or write access to the configuration files specifically, not just the parent directoriesAffected if Standard users are members of groups granted write access to these configuration files
A user is affected if the F-Secure Support Tool is installed and configuration files or directories used by it are writable by standard (non-privileged) users, enabling potential 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.
From vendor dataApply vendor-supplied patches for F-Secure Support Tool. As a compensating control, restrict file system permissions on configuration directories to prevent standard users from modifying configuration files used by privileged tools.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-44750 — 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-2021-44750 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