CVE-2023-47172
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 · uneditedCertain WithSecure products allow Local Privilege Escalation. This affects WithSecure Client Security 15, WithSecure Server Security 15, WithSecure Email and Server Security 15, and WithSecure Elements Endpoint Protection 17 and later.
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 confidenceA local privilege escalation vulnerability in WithSecure endpoint security products (Client Security 15, Server Security 15, Email and Server Security 15, and Elements Endpoint Protection 17 and later) allows a local authenticated attacker to gain elevated privileges on the affected system.
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>= 15>= 17>= 15>= 15CVSS 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.
-
Identify installed WithSecure productsOpen Programs and Features (appwiz.cpl) or check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'WithSecure', 'F-Secure', 'Client Security', 'Server Security', 'Email And Server Security', or 'Elements Endpoint Protection'Affected if Any WithSecure product listed in Programs and Features is found
-
Determine installed version of WithSecure Client SecurityCheck registry key HKLM\SOFTWARE\WithSecure\Client\Version or HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductCode} for the DisplayVersion valueAffected if Version is 15.x or higher
-
Determine installed version of WithSecure Elements Endpoint ProtectionCheck registry key HKLM\SOFTWARE\WithSecure\Elements\Endpoint\Version or check the product's About/Version information in the system tray or control panel appletAffected if Version is 17.x or higher
-
Determine installed version of WithSecure Server Security or Email And Server SecurityCheck registry key HKLM\SOFTWARE\WithSecure\Server\Version or HKLM\SOFTWARE\WithSecure\EmailAndServer\Version, or check Programs and Features for the specific product entryAffected if Version is 15.x or higher
Your environment is affected if any WithSecure product (Client Security, Server Security, Email and Server Security, or Elements Endpoint Protection) is installed with a version matching or exceeding the affected version ranges.
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 or updates for the affected WithSecure products. Until patches are available, restrict local access to trusted administrators and monitor for suspicious process activity.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47172 — 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-2023-47172 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