{"uuid": "386c28d0-a649-4ab1-8f86-fa25eeb8209e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-0847", "type": "seen", "source": "https://t.me/hacking_Attack/46518", "content": "Black Hat Ethical Hacking\nMost QNAP NAS Devices Affected by \u2018Dirty Pipe\u2019 Linux Flaw\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png Most QNAP NAS Devices Affected by \u2018Dirty Pipe\u2019 Linux FlawPost Views: 1 \nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/02/Patreon.png \nReading Time: 2 Minutes\nThe \u201cDirty Pipe\u201d\u00a0Linux kernel flaw\u00a0\u2013 a high-severity vulnerability in all major distros that grants root access to unprivileged users who have local access \u2013 affects most of QNAP\u2019s network-attached storage (NAS) appliances.\nThe \u201cDirty Pipe\u201d Linux kernel flaw\u00a0\u2013 a high-severity vulnerability in all major distros that grants root access to unprivileged users who have local access \u2013 affects most of QNAP\u2019s network-attached storage (NAS) appliances, the Taiwanese manufacturer warned on Monday.\n\nDirty Pipe, a recently reported local privilege-escalation vulnerability, affects the Linux kernel on QNAP NAS running QTS 5.0.x and QuTS hero h5.0.x, QNAP advised. If exploited, an unprivileged, local user can gain admin privileges and inject malicious code.\n\nThe situation is grim: QNAP said\u00a0that as of yesterday, there was no mitigation.\n\n\u201cCurrently there is no mitigation available for this vulnerability. We recommend users to check back and install security updates as soon as they become available.\u201d \u2013QNAP\nSee Also: Complete Offensive Security and Ethical Hacking Course\nThe following versions of QTS and QuTS hero are affected:\n\n* QTS 5.0.x on all QNAP x86-based NAS and certain QNAP ARM-based NAS\n* QuTS hero h5.0.x on all QNAP x86-based NAS and certain QNAP ARM-based NAS\n\nQNAP NAS running QTS 4.x aren\u2019t affected. The company pointed users to a full list of the affected models: check \u201cKernel Version 5.10.60\u201d in this link, it said in its advisory.\n\n\u201cQNAP is thoroughly investigating the vulnerability. We will release security updates and provide further information as soon as possible,\u201d the advisory said. As Bad as It SoundsSecurity researcher Max Kellermann of CM4all discovered and reported\u00a0the bug eight days ago. Tracked as CVE-2022-0847, the vulnerability has been in the Linux kernel since 5.8. Fortunately, the vulnerability has been\u00a0fixed\u00a0in Linux kernel 5.10.102, 5.15.25, and 5.16.11. If you\u2019re at or above that version, you\u2019re fine.\n\nBut as pointed out by Linux news site Linuxiac, Dirty Pipe doesn\u2019t just threaten Linux machines: Since Android is based on the Linux kernel, any device\u00a0running version\u00a05.8 or later is also vulnerable, endangering a slew of people. Linuxiac pointed to the Google Pixel 6 and Samsung Galaxy S22 as examples: The massively popular phones use Linux kernel 5.10.43, which makes them vulnerable.\n\nDirty Pipe allows for overwriting of data in arbitrary read-only files, which leads to privilege escalation because unprivileged processes can inject code into root processes.\nSee Also: Kali Linux 2022.1 Release with Visual Updates, New Tools, Legacy SSH The Common Vulnerabilities and Exposures (CVE) database describes it as a \u201cflaw in the way the \u2018flags\u2019 member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe and push_pipe functions in the Linux kernel and could thus contain stale values.\n\n\u201cAn unprivileged local user could use this flaw to write to pages in the page cache backed by read only files and as such escalate their privileges on the system,\u201d according to the CVE description.\n\n\u201cIf you\u2019re not sure what that means but you think it sounds bad \u2013 you are correct!\u201d MalwareBytes malware intelligence researcher Pieter Arntz wrote\u00a0on Friday.\n\nKeiderman offered a full technical analysis in his CM4all post. For his part, Arntz gave this TL;DR version: \u201cThe confusion in t[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-02T01:02:03.820881Z"}