# CVE-2019-3827: Missing authorization in gvfs > Privileged users can modify arbitrary system files without authentication if no agent is running, enabling privilege escalation in uncommon configurations. - **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 25 Mar 2019 - **Updated:** 4 Aug 2024 - **Also known as:** DEBIAN-CVE-2019-3827, GHSA-4782-6x7j-q79q, MGASA-2019-0080, RHSA-2019:1517, RHSA-2019:2145, SUSE-SU-2019:0438-1, UBUNTU-CVE-2019-3827, USN-3888-1, openSUSE-SU-2019:0261-1 ## What is CVE-2019-3827? CVE-2019-3827 is a high-severity missing authorization vulnerability in [UNKNOWN] gvfs, published on 25 Mar 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description An incorrect permission check in the admin backend in gvfs before version 1.39.4 was found that allows reading and modify arbitrary files by privileged users without asking for password when no authentication agent is running. This vulnerability can be exploited by malicious programs running under privileges of users belonging to the wheel group to further escalate its privileges by modifying system files without user's knowledge. Successful exploitation requires uncommon system configuration. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2019-3827? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gvfs` | Red Hat:enterprise_linux:7::client | All versions | 0:1.36.2-3.el7 | | `gvfs-afc` | Red Hat:enterprise_linux:7::client | All versions | 0:1.36.2-3.el7 | | `gvfs-afp` | Red Hat:enterprise_linux:7::client | All versions | 0:1.36.2-3.el7 | | `gvfs-archive` | Red Hat:enterprise_linux:7::client | All versions | 0:1.36.2-3.el7 | | `gvfs-client` | Red Hat:enterprise_linux:7::client | All versions | 0:1.36.2-3.el7 | | `gvfs-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:1.36.2-3.el7 | | `gvfs-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:1.36.2-3.el7 | | `gvfs-fuse` | Red Hat:enterprise_linux:7::client | All versions | 0:1.36.2-3.el7 | | `gvfs-goa` | Red Hat:enterprise_linux:7::client | All versions | 0:1.36.2-3.el7 | | `gvfs-gphoto2` | Red Hat:enterprise_linux:7::client | All versions | 0:1.36.2-3.el7 | | `gvfs-mtp` | Red Hat:enterprise_linux:7::client | All versions | 0:1.36.2-3.el7 | | `gvfs-smb` | Red Hat:enterprise_linux:7::client | All versions | 0:1.36.2-3.el7 | | `gvfs-tests` | Red Hat:enterprise_linux:7::client | All versions | 0:1.36.2-3.el7 | | `gvfs` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.36.2-3.el7 | | `gvfs-afc` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.36.2-3.el7 | | `gvfs-afp` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.36.2-3.el7 | | `gvfs-archive` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.36.2-3.el7 | | `gvfs-client` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.36.2-3.el7 | | `gvfs-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.36.2-3.el7 | | `gvfs-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.36.2-3.el7 | | `gvfs-fuse` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.36.2-3.el7 | | `gvfs-goa` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.36.2-3.el7 | | `gvfs-gphoto2` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.36.2-3.el7 | | `gvfs-mtp` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.36.2-3.el7 | | `gvfs-smb` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.36.2-3.el7 | | `gvfs-tests` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.36.2-3.el7 | | `gvfs` | Red Hat:enterprise_linux:7::server | All versions | 0:1.36.2-3.el7 | | `gvfs-afc` | Red Hat:enterprise_linux:7::server | All versions | 0:1.36.2-3.el7 | | `gvfs-afp` | Red Hat:enterprise_linux:7::server | All versions | 0:1.36.2-3.el7 | | `gvfs-archive` | Red Hat:enterprise_linux:7::server | All versions | 0:1.36.2-3.el7 | | `gvfs-client` | Red Hat:enterprise_linux:7::server | All versions | 0:1.36.2-3.el7 | | `gvfs-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1.36.2-3.el7 | | `gvfs-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:1.36.2-3.el7 | | `gvfs-fuse` | Red Hat:enterprise_linux:7::server | All versions | 0:1.36.2-3.el7 | | `gvfs-goa` | Red Hat:enterprise_linux:7::server | All versions | 0:1.36.2-3.el7 | | `gvfs-gphoto2` | Red Hat:enterprise_linux:7::server | All versions | 0:1.36.2-3.el7 | | `gvfs-mtp` | Red Hat:enterprise_linux:7::server | All versions | 0:1.36.2-3.el7 | | `gvfs-smb` | Red Hat:enterprise_linux:7::server | All versions | 0:1.36.2-3.el7 | | `gvfs-tests` | Red Hat:enterprise_linux:7::server | All versions | 0:1.36.2-3.el7 | | `gvfs` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.36.2-3.el7 | Products: Gnome Gvfs. ## How do I fix CVE-2019-3827? Upgrade to a fixed version. ## Is CVE-2019-3827 being exploited? There is no known exploitation of CVE-2019-3827 in the wild and no public exploit code. ## Other vulnerabilities in [UNKNOWN] gvfs - [CVE-2019-12448](https://insights.sbomify.com/CVE-2019-12448/): Race condition in n/a (high 8.1) - [CVE-2019-12795](https://insights.sbomify.com/CVE-2019-12795/): Missing authorization in n/a (high 7.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-3827 and fix it if it is affected. What it is: CVE-2019-3827 is a high-severity missing authorization vulnerability in [UNKNOWN] gvfs, published on 25 Mar 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-3827 in the wild and no public exploit code. Affected product: [UNKNOWN] gvfs. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-3827/ (Markdown: https://insights.sbomify.com/CVE-2019-3827/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-3827 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-3827 - OSV: https://osv.dev/vulnerability/CVE-2019-3827 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-3827/ Summaries are generated and may contain mistakes; the official description above is the record.