Local Privilege Escalation in cloudflared
High severity
GitHub Reviewed
Published
Sep 16, 2020
in
cloudflare/cloudflared
•
Updated Mar 2, 2023
Package
Affected versions
< 0.0.0-20200820025921-9323844ea773
Patched versions
0.0.0-20200820025921-9323844ea773
Description
Published by the National Vulnerability Database
Oct 2, 2020
Reviewed
May 24, 2021
Published to the GitHub Advisory Database
May 24, 2021
Last updated
Mar 2, 2023
In
cloudflared
versions < 2020.8.1 (corresponding to 0.0.0-20200820025921-9323844ea773 on pkg.go.dev) on Windows, if an administrator has startedcloudflared
and set it to read configuration files from a certain directory, an unprivileged user can exploit a misconfiguration in order to escalate privileges and execute system-level commands. The misconfiguration was due to the way thatcloudflared
reads its configuration file. One of the locations thatcloudflared
reads from (C:\etc) is not a secure by default directory due to the fact that Windows does not enforce access controls on this directory without further controls applied. A malformed config.yaml file can be written by any user. Upon reading this config,cloudflared
would output an error message to a log file defined in the malformed config. The user-controlled log file location could be set to a specific location that Windows will execute when any user logs in.References