CVE-2022-27535
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 · uneditedKaspersky VPN Secure Connection for Windows version up to 21.5 was vulnerable to arbitrary file deletion via abuse of its 'Delete All Service Data And Reports' feature by the local authenticated attacker.
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 confidenceKaspersky VPN Secure Connection for Windows versions up to 21.5 contains a path traversal vulnerability in its 'Delete All Service Data And Reports' feature that allows an authenticated local attacker to delete arbitrary files on the system due to insufficient validation of file paths provided to the deletion function.
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< 21.6CVSS 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 Kaspersky VPN Secure Connection is installedOpen Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Kasper*VPN*"}' in PowerShell to check for the productAffected if The product is not found in installed programs
-
Check the installed version numberRight-click the Kaspersky VPN Secure Connection application in the system tray, select 'About', or check the version in Programs and Features. Compare against the vulnerable range: versions prior to 21.6 are affectedAffected if Installed version is earlier than 21.6 (for example, 21.5, 21.3, etc.)
-
Confirm the Delete All Service Data And Reports feature existsOpen Kaspersky VPN Secure Connection, navigate to Settings or the menu options to locate the 'Delete All Service Data And Reports' feature typically found under settings or account managementAffected if The feature is present in the installed version and version is below 21.6
-
Verify local authentication requirementThe vulnerability requires an authenticated local user session. Confirm the system allows local user accounts that could potentially access the VPN applicationAffected if Local user accounts exist on the system with access to the VPN application
A system is affected if Kaspersky VPN Secure Connection for Windows is installed with a version number lower than 21.6 and the Delete All Service Data And Reports feature is accessible to local authenticated users.
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 · scoped21.6
Update Kaspersky VPN Secure Connection to version 21.6 or later to receive the patch that properly validates file paths before deletion.
21.6
- Upgrade Kaspersky VPN Secure Connection for Windows to version 21.6 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27535 — 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-27535 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