CVE-2023-1314
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 · uneditedA vulnerability has been discovered in cloudflared's installer (<= 2023.3.0) for Windows 32-bits devices that allows a local attacker with no administrative permissions to escalate their privileges on the affected device. This vulnerability exists because the MSI installer used by cloudflared relied on a world-writable directory. An attacker with local access to the device (without Administrator rights) can use symbolic links to trick the MSI installer into deleting files in locations that the attacker would otherwise have no access to. By creating a symlink from the world-writable directory to the target file, the attacker can manipulate the MSI installer's repair functionality to delete the target file during the repair process. Exploitation of this vulnerability could allow an attacker to delete important system files or replace them with malicious files, potentially leading to the affected device being compromised. The cloudflared client itself is not affected by this vulnerability, only the installer for 32-bit Windows devices.
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 confidenceLocal privilege escalation vulnerability in cloudflared MSI installer for 32-bit Windows (versions 2023.3.0 and earlier). The installer relies on a world-writable directory, allowing an attacker to create symbolic links that manipulate the MSI repair functionality to delete or replace arbitrary files they lack permission to modify.
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< 2023.3.1CVSS 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.
-
Check if running 32-bit WindowsRun 'systeminfo' in command prompt and look for 'System Type: x86' (32-bit) or 'System Type: x64' (64-bit). Alternatively, check the Program Files folder - 32-bit apps on 64-bit Windows are in 'C:\Program Files (x86)\'Affected if System is 32-bit Windows (x86)
-
Check if cloudflared was installed via MSI installerCheck for cloudflared in Windows Installer logs (C:\Windows\Temp\MSI*.log) or look for cloudflared in Add/Remove Programs and note the installation method. Check C:\Program Files (x86)\cloudflared or C:\Program Files\cloudflared for installed files.Affected if cloudflared was installed using the MSI installer package on 32-bit Windows
-
Determine installed cloudflared versionRun 'cloudflared --version' in command prompt, or check the version in Add/Remove Programs, or inspect the file properties of the cloudflared.exe in the installation directory.Affected if Installed version is 2023.3.0 or earlier on 32-bit Windows with MSI installation
-
Verify MSI installer was used (alternative check)Check the Windows Installer registry key at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{cloudflared GUID} for 'InstallerType' or look for evidence in C:\Windows\Temp of MSI installer logs containing 'cloudflared'Affected if MSI installer was the deployment method used
A 32-bit Windows system with cloudflared installed via MSI installer version 2023.3.0 or earlier is affected by this vulnerability in the installer.
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 · scoped2023.3.1
Upgrade cloudflared installer to a version newer than 2023.3.0 for 32-bit Windows systems; the cloudflared client itself is unaffected.
2023.3.1 or later
- Download cloudflared installer version 2023.3.1 or later from the official Cloudflare repository
- Verify the installer checksum if available
- Uninstall the vulnerable cloudflared version if currently installed
- Run the new installer with Administrator privileges to apply the updated version
- Verify the installation completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1314 — 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-1314 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