dbcve.org
AntivirusApplication · Vipre

CVE-2023-32177

HIGH · 7.8 CVSS v3.0 Published 2024-05-03
Fix available
A fix is available. Upgrade to 12.0.1.203 or later.
See remediation →
80/100
Remediation priority · High
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
VIPRE Antivirus Plus DeleteHistoryFile Directory Traversal Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of VIPRE Antivirus Plus. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the DeleteHistoryFile method. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. . Was ZDI-CAN-19395.

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

Directory traversal vulnerability in VIPRE Antivirus Plus DeleteHistoryFile method allows local attackers to manipulate user-supplied paths lacking proper validation, enabling privilege escalation from low-privileged user to SYSTEM context and arbitrary code execution.

MitigationApply vendor-provided security patch for VIPRE Antivirus Plus; verify DeleteHistoryFile method now properly validates and sanitizes file paths before operations.

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
AntivirusApplication
Affected:< 12.0.1.203

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

CVSS:3.0/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 checks

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

  1. Confirm VIPRE Antivirus Plus installation
    Locate the VIPRE Antivirus Plus installation directory or check program listings
    Affected if VIPRE Antivirus Plus is not installed on the system
  2. Identify installed VIPRE version
    Use system tools to view the installed version of VIPRE Antivirus Plus (typically available in program metadata, about dialog, or installation directory)
    Affected if The installed version is lower than 12.0.1.203
  3. Verify vulnerable component presence
    Check for the presence of the DeleteHistoryFile method or related component within the VIPRE installation
    Affected if The DeleteHistoryFile component exists in the installation and is accessible to local users

The system is affected if VIPRE Antivirus Plus is installed with a version prior to 12.0.1.203 and the DeleteHistoryFile component is present and accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 12.0.1.203 or later
Fixed in 12.0.1.203
Interim mitigation

Apply vendor-provided security patch for VIPRE Antivirus Plus; verify DeleteHistoryFile method now properly validates and sanitizes file paths before operations.

Recommended fix High confidence

VIPRE Antivirus Plus version 12.0.1.203 or later

  1. 1. Open VIPRE Antivirus Plus on the affected system
  2. 2. Navigate to the Settings or About section to confirm the current version is below 12.0.1.203
  3. 3. Open a web browser and navigate to the official VIPRE support or download page (e.g., success.vipre.com or vipre.com)
  4. 4. Download the latest version of VIPRE Antivirus Plus (ensure version 12.0.1.203 or later)
  5. 5. Run the installer and follow the prompts to update the software
  6. 6. Restart the system if prompted
  7. 7. Verify the installed version is now 12.0.1.203 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Antivirus Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32177 — 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-2023-32177 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