CVE-2023-34298
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 · uneditedPulse Secure Client SetupService Directory Traversal Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Pulse Secure Client. 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 SetupService. 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 the service. Was ZDI-CAN-17687.
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 confidenceA directory traversal vulnerability in Pulse Secure Client's SetupService allows local attackers with low-privileged code execution to escalate privileges. The flaw stems from insufficient validation of user-supplied paths before file operations, enabling arbitrary code execution in the service context.
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< 9.1= 9.1= 9.1= 22.4.1439= 22.2= 22.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Ivanti Pulse Secure product and versionCheck the installed programs list in Windows Control Panel > Programs and Features, or use 'wmic product get name,version' or review the executable properties of the Pulse Secure client binary (typically named pulsesec.exe, pulse.exe, or related DLLs in the installation directory)Affected if The installed version matches any of these: Pulse Secure Desktop Client versions < 9.1 or = 9.1; Pulse Secure Installer Service version 9.1 or 22.4.1439; Secure Access Client version 22.2 or 22.3
-
Locate and verify the SetupService existsOpen Services.msc and look for a service named 'Pulse Secure Setup Service' or 'Ivanti Setup Service', or run 'sc queryex type= service state= all' and filter for 'setup' or 'pulse' related servicesAffected if The SetupService is present on the system (the vulnerability exists in this service component)
-
Determine the context under which SetupService runsRun 'sc qc <service_name>' to query the service configuration, noting the binary path and the SERVICE_START_NAME (the account the service runs under, typically SYSTEM or a service account)Affected if The service runs with elevated privileges (SYSTEM, LocalSystem, or a privileged service account) and the vulnerability is present in the affected versions
-
Check file system permissions on the Pulse Secure installation directoryRight-click the installation folder (commonly C:\Program Files\Pulse Secure or C:\Program Files (x86)\Pulse Secure), select Properties > Security, and review which users/groups have Write or Modify permissions, particularly for low-privileged accountsAffected if Low-privileged or non-admin users have Write or Modify access to directories used by the SetupService for file operations
Your environment is affected if you have any of the listed affected versions of Ivanti Pulse Secure Desktop Client, Pulse Secure Installer Service, or Secure Access Client AND the SetupService is installed and runs with elevated privileges.
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 data9.1
Apply vendor-provided patches when available; until then, restrict file system permissions on the service directory and monitor for suspicious file operations targeting the SetupService.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34298 — 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-34298 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