Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/vulndb: potential Go vuln in github.com/cloudflare/cloudflared: GHSA-hgwp-4vp4-qmm2 #1392

Closed
GoVulnBot opened this issue Jan 9, 2023 · 1 comment

Comments

@GoVulnBot
Copy link

In GitHub Security Advisory GHSA-hgwp-4vp4-qmm2, there is a vulnerability in the following Go packages or modules:

Unit Fixed Vulnerable Ranges
github.com/cloudflare/cloudflared 2020.8.1 < 2020.8.1

Cross references:

See doc/triage.md for instructions on how to triage this report.

modules:
  - module: TODO
    versions:
      - fixed: 2020.8.1
    packages:
      - package: github.com/cloudflare/cloudflared
description: In `cloudflared` versions < 2020.8.1 on Windows, if an administrator
    has started `cloudflared` 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 that `cloudflared` reads its configuration file. One of the locations
    that `cloudflared` 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.
cves:
  - CVE-2020-24356
ghsas:
  - GHSA-hgwp-4vp4-qmm2

@tatianab
Copy link
Contributor

tatianab commented Jan 9, 2023

Duplicate of #845

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants