# CVE-2017-8422: Auth bypass in n/a > Local attackers can gain root privileges by spoofing callerID in KDE kdelibs and KAuth privileged helper applications. - **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 May 2017 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2017-8422, GHSA-3x3g-jj7x-gr2f, MGASA-2017-0274, RHSA-2017:1264, SUSE-SU-2017:1335-1, UBUNTU-CVE-2017-8422, USN-3286-1, openSUSE-SU-2017:1254-1, openSUSE-SU-2017:1272-1 ## What is CVE-2017-8422? CVE-2017-8422 is a high-severity authentication bypass vulnerability in n/a, published on 17 May 2017. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description KDE kdelibs before 4.14.32 and KAuth before 5.34 allow local users to gain root privileges by spoofing a callerID and leveraging a privileged helper app. Weakness: CWE-290 (Authentication Bypass by Spoofing) ## Which versions are affected by CVE-2017-8422? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kdelibs` | Red Hat:enterprise_linux:7::client | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-apidocs` | Red Hat:enterprise_linux:7::client | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-common` | Red Hat:enterprise_linux:7::client | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-devel` | Red Hat:enterprise_linux:7::client | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-ktexteditor` | Red Hat:enterprise_linux:7::client | All versions | 6:4.14.8-6.el7_3 | | `kdelibs` | Red Hat:enterprise_linux:7::computenode | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-apidocs` | Red Hat:enterprise_linux:7::computenode | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-common` | Red Hat:enterprise_linux:7::computenode | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-ktexteditor` | Red Hat:enterprise_linux:7::computenode | All versions | 6:4.14.8-6.el7_3 | | `kdelibs` | Red Hat:enterprise_linux:7::server | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-apidocs` | Red Hat:enterprise_linux:7::server | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-common` | Red Hat:enterprise_linux:7::server | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-devel` | Red Hat:enterprise_linux:7::server | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-ktexteditor` | Red Hat:enterprise_linux:7::server | All versions | 6:4.14.8-6.el7_3 | | `kdelibs` | Red Hat:enterprise_linux:7::workstation | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-apidocs` | Red Hat:enterprise_linux:7::workstation | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-common` | Red Hat:enterprise_linux:7::workstation | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 6:4.14.8-6.el7_3 | | `kdelibs-ktexteditor` | Red Hat:enterprise_linux:7::workstation | All versions | 6:4.14.8-6.el7_3 | | `kdelibs4` | SUSE:Linux Enterprise Desktop 12 SP1 | All versions | 4.12.0-10.1 | | `kdelibs4` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 4.12.0-10.1 | | `kdelibs4` | SUSE:Linux Enterprise Server 12 SP1 | All versions | 4.12.0-10.1 | | `kdelibs4` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 4.12.0-10.1 | | `kdelibs4` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 4.12.0-10.1 | | `kdelibs4` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 4.12.0-10.1 | | `kdelibs4` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 4.12.0-10.1 | | `kauth` | SUSE:Package Hub 12 SP1 | All versions | 5.26.0-6.1 | | `kauth` | SUSE:Package Hub 12 SP1 | All versions | 5.26.0-6.1 | | `kdelibs4` | SUSE:Package Hub 12 SP1 | All versions | 4.14.25-8.2 | | `kdelibs4` | SUSE:Package Hub 12 SP1 | All versions | 4.14.25-8.2 | | `kdelibs4-apidocs` | SUSE:Package Hub 12 SP1 | All versions | 4.14.25-8.2 | | `kdelibs4-apidocs` | SUSE:Package Hub 12 SP1 | All versions | 4.14.25-8.2 | | `kauth` | SUSE:Package Hub 12 SP2 | All versions | 5.26.0-6.1 | | `kauth` | SUSE:Package Hub 12 SP2 | All versions | 5.26.0-6.1 | | `kdelibs4` | SUSE:Package Hub 12 SP2 | All versions | 4.14.25-8.2 | Products: Kde Kauth, Kde Kdelibs. ## How do I fix CVE-2017-8422? Upgrade to a fixed version. ## Is CVE-2017-8422 being exploited? There is no known exploitation of CVE-2017-8422 in the wild and no public exploit code. Public exploit code: - KDE 4/5 - 'KAuth' Local Privilege Escalation (exploitdb) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-8422 and fix it if it is affected. What it is: CVE-2017-8422 is a high-severity authentication bypass vulnerability in n/a, published on 17 May 2017. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-8422 in the wild and no public exploit code. Affected product: n/a. 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-2017-8422/ (Markdown: https://insights.sbomify.com/CVE-2017-8422/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-8422 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-8422 - OSV: https://osv.dev/vulnerability/CVE-2017-8422 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-8422/ Summaries are generated and may contain mistakes; the official description above is the record.