{"vulnerability": "cve-2021-3619", "sightings": [{"uuid": "29a51147-79c0-4e45-a3cb-52f9ff9f2886", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-36193", "type": "seen", "source": "https://t.me/cibsecurity/36694", "content": "\u203c CVE-2021-36193 \u203c\n\nMultiple stack-based buffer overflows in the command line interpreter of FortiWeb before 6.4.2 may allow an authenticated attacker to achieve arbitrary code execution via specially crafted commands.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-02-02T14:28:20.000000Z"}, {"uuid": "f2348872-62ef-4f07-ba9d-c511f46adf95", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-36195", "type": "seen", "source": "https://t.me/cibsecurity/33637", "content": "\u203c CVE-2021-36195 \u203c\n\nMultiple command injection vulnerabilities in the command line interpreter of FortiWeb versions 6.4.1, 6.4.0, 6.3.0 through 6.3.15, 6.2.0 through 6.2.6, and 6.1.0 through 6.1.2 may allow an authenticated attacker to execute arbitrary commands on the underlying system shell via specially crafted command arguments.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-12-08T22:22:56.000000Z"}, {"uuid": "d64292de-4ff9-4c66-92ca-ded643be716d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-36198", "type": "seen", "source": "https://t.me/cibsecurity/33395", "content": "\u203c CVE-2021-36198 \u203c\n\nSuccessful exploitation of this vulnerability could allow an unauthorized user to access sensitive data.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-12-06T20:20:52.000000Z"}, {"uuid": "39cbcfa5-a078-4f87-a0a3-a044ed04ba53", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-36190", "type": "seen", "source": "https://t.me/cibsecurity/33584", "content": "\u203c CVE-2021-36190 \u203c\n\nA unintended proxy or intermediary ('confused deputy') in Fortinet FortiWeb version 6.4.1 and below, 6.3.15 and below allows an unauthenticated attacker to access protected hosts via crafted HTTP requests.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-12-08T16:22:48.000000Z"}, {"uuid": "ee64dceb-577a-4b9d-a446-40d97f743643", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-36191", "type": "seen", "source": "https://t.me/cibsecurity/33579", "content": "\u203c CVE-2021-36191 \u203c\n\nA url redirection to untrusted site ('open redirect') in Fortinet FortiWeb version 6.4.1 and below, 6.3.15 and below allows attacker to use the device as proxy via crafted GET parameters in requests to error handlers\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-12-08T16:22:40.000000Z"}, {"uuid": "28c0a483-1ab6-4c30-bee0-22b7fb7d268e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-36192", "type": "seen", "source": "https://t.me/cibsecurity/31711", "content": "\u203c CVE-2021-36192 \u203c\n\nAn exposure of sensitive information to an unauthorized actor [CWE-200] vulnerability in FortiManager 7.0.1 and below, 6.4.6 and below, 6.2.x, 6.0.x, 5.6.0 may allow a FortiGate user to see scripts from other ADOMS.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-11-03T13:23:35.000000Z"}, {"uuid": "b4188531-620d-464e-bc3b-322baff11309", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-36195", "type": "seen", "source": "https://t.me/hacking_Attack/3429", "content": "Black Hat Ethical Hacking\nLegacy QNAP NAS Devices Vulnerable to Zero-Day Attack\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Legacy QNAP NAS Devices Vulnerable to Zero-Day AttackPost Views: 63 \nstyle=\"display:block\"\n data-ad-client=\"ca-pub-6620833063853657\"\n data-ad-slot=\"8337846400\"\n data-ad-format=\"auto\"\n data-full-width-responsive=\"true\"> \nReading Time: 1 Minute\nTwo critical zero-day bugs affect legacy QNAP Systems storage hardware, and expose devices to remote unauthenticated attackers.\nThe bugs, tracked as CVE-2020-2509 and CVE-2021-36195, impact QNAP\u2019s model TS-231 network attached storage (NAS) hardware, allowing an attacker to manipulate stored data and hijack the device. The vulnerabilities, also impact some non-legacy QNAP NAS gear. However, it is important to note that patches are available for non-legacy QNAP NAS hardware.\n\nA patch for the now-retired QNAP model TS-231 NAS device, first released in 2015, is scheduled to be released within weeks, QNAP representatives told Threatpost.\n\nPatches for current model QNAP devices need to be downloaded from the QNAP download center and applied manually. Zero-Day DisclosureBoth bugs were disclosed on Wednesday by SAM Seamless Network researchers, who released limited technical details. The disclosure was ahead of official QNAP public disclosure of the vulnerabilities, and was in line with SAM Seamless Network\u2019s disclosure policy of giving a vendor three months to disclose vulnerability details. Both flaws were found in the Oct. and Nov. 2020 timeframe and made public Wednesday.\n\n\u201cWe reported both vulnerabilities to QNAP with a four-month grace period to fix them,\u201d researchers wrote. \u201cDue to the seriousness of the vulnerabilities, we decided not to disclose the full details yet, as we believe this could cause major harm to tens of thousands of QNAP devices exposed to the internet.\u201d\nSee Also: Apple, Google Both Track Mobile Telemetry Data, Despite Users Opting Out\nQNAP would not specifically say how many additional legacy NAS devices may be impacted. The company, in a statement to Threatpost said: \u201cThere are many hardware models of NAS in QNAP. (See: https://www.qnap.com/en/product/eol.php). In the list, you can find the models, the period of hardware repair or replacement, the supported OS and App updates and maintenance and the status of technical support and security updates. Most of the models, the security update could be upgraded to the latest version, i.e. QTS 4.5.2. However, some old hardware models have limits of firmware upgrade. For example, TS-EC1679U-SAS-RP could support only the legacy QTS 4.3.4.\u201d Breaking Down QNAP Bug OneTracked as CVE-2020-2509, this remote code execution (RCE) bug is tied to firmware used in both old and new hardware, according to QNAP. Firmware versions prior to QTS 4.5.2.1566 (build 20210202) and QTS 4.5.1.1495 (build 20201123) are affected. Patches for current (non-legacy) hardware can be downloaded via QTS 4.5.2.1566 (ZIP) and QTS 4.5.1.1495 (ZIP).\n\nThe bug (CVE-2020-2509) resides in the NAS web server (default TCP port 8080), according to researchers.\n\n\u201cPrevious RCE attacks on QNAP NAS models relied on web pages which do not require prior authentication, and run/trigger code in server-side. We\u2019ve therefore inspected some CGI files (which implement such pages) and fuzzed a few of the more relevant ones,\u201d researchers described.\n\nThey said that during the inspection, they were able to fuzz the web server with customized HTTP requests to different CGI pages, focusing on ones that didn\u2019t require prior authentication. \u201cWe\u2019ve been able to generate an interesting scenario, which triggers remote code execution indirectly (i.e[...]", "creation_timestamp": "2026-09-01T20:02:49.765458Z"}, {"uuid": "04de12f1-5033-4739-9d2c-fa91563f2f53", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-36195", "type": "seen", "source": "https://t.me/hacking_Attack/3430", "content": "., triggers some behavior in other processes),\u201d researchers wrote.\nSee Also: Information Security Tool: Chameleon A fix for the vulnerability, suggested by researchers, is \u201cadding input sanitizations to some core processes and library APIs, but it has not been fixed as of this writing.\u201d Breaking Down QNAP Bug TwoThe second bug, tracked as CVE-2021-36195, is an unauthenticated RCE and arbitrary file-write flaw. It impacts QNAP TS-231\u2019s latest firmware (version 4.3.6.1446), released in September.\n\nThe flaw allows two types of attacks. One allows a remote attacker \u2013 with access to the web server (default port 8080) \u2013 to execute arbitrary shell commands, without prior knowledge of the web credentials.\n\nThe second attack \u201callows a remote attacker with access to the DLNA server (default port 8200) to create arbitrary file data on any (non-existing) location, without any prior knowledge or credentials. It can also be elevated to execute arbitrary commands on the remote NAS as well,\u201d according to researchers at SAM Seamless Network.\n\nTo exploit the bug, researchers created a proof-of-concept attack. \u201c[We used] a python script that we wrote in order to hack into the device. We achieve full takeover of the device by using a simple reverse shell technique. After that, we access a file that\u2019s stored on the QNAP storage. Any file stored can be accessed similarly.\u201d\n\nQNAP said a fix for supported hardware can be downloaded from the QNAP App Center and is identified as Multimedia Console 1.3.4. See Also: Hacking Stories: When two young hackers played war games with PentagonQNAP Patch Timeline\u201cCurrently, we have released the fix in the latest firmware and related app,\u201d QNAP representatives told Threatpost. \u201cSince the severity level is high, we would like to release the security update for legacy versions. It is expected to be available in a week. In addition, we hope there will be another week for users\u2019 updates.\u201d\nSource: https://threatpost.com (Click Link)style=\"display:block\"\n data-ad-client=\"ca-pub-6620833063853657\"\n data-ad-slot=\"8337846400\"\n data-ad-format=\"auto\"\n data-full-width-responsive=\"true\"> Recent News* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/04/iphone-privacy-90x90.jpg Apple, Google Both Track Mobile Telemetry Data, Despite Users Opting Out1 day ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/Monero-Mining-90x90.png Malicious Docker Cryptomining Images Rack Up 20M Downloads2 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/phph-90x90.jpg PHP Infiltrated with Backdoor Malware3 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/ransomware_global_small-90x90.jpg Insurance Giant CNA Hit with Novel Ransomware Attack4 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/Microsoft-Teams-90x90.jpg Microsoft Offers Up To $30K For Teams Bugs1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/thrive-themes-1030x391-1-90x90.png Active Exploits Hit WordPress Sites Vulnerable to Thrive Themes Flaws1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/HL-color-90x90.jpg Hobby Lobby Exposes Customer Data in Cloud Misconfiguration1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/adobe_coldfusion-700x412-e1542041238507-90x90.jpg Adobe Fixes Critical ColdFusion Flaw in Emergency Update1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/Clubhouse-e1614022265127-90x90.jpg Bogus Android Clubhouse App Drops Credential-Swiping Malware2 weeks ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/apple-security-90x90.jpg Trojanized Xcode Project Slips MacOS Malware to Apple Developers2 weeks ago\nThe post Legacy QNAP NAS Devices Vulnerable to Zero-Day Attack first[...]", "creation_timestamp": "2026-09-01T20:02:49.815591Z"}, {"uuid": "615713ac-245b-41e4-be44-2c8ae3e18201", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-36195", "type": "seen", "source": "https://t.me/hacking_Attack/3430", "content": "., triggers some behavior in other processes),\u201d researchers wrote.\nSee Also: Information Security Tool: Chameleon A fix for the vulnerability, suggested by researchers, is \u201cadding input sanitizations to some core processes and library APIs, but it has not been fixed as of this writing.\u201d Breaking Down QNAP Bug TwoThe second bug, tracked as CVE-2021-36195, is an unauthenticated RCE and arbitrary file-write flaw. It impacts QNAP TS-231\u2019s latest firmware (version 4.3.6.1446), released in September.\n\nThe flaw allows two types of attacks. One allows a remote attacker \u2013 with access to the web server (default port 8080) \u2013 to execute arbitrary shell commands, without prior knowledge of the web credentials.\n\nThe second attack \u201callows a remote attacker with access to the DLNA server (default port 8200) to create arbitrary file data on any (non-existing) location, without any prior knowledge or credentials. It can also be elevated to execute arbitrary commands on the remote NAS as well,\u201d according to researchers at SAM Seamless Network.\n\nTo exploit the bug, researchers created a proof-of-concept attack. \u201c[We used] a python script that we wrote in order to hack into the device. We achieve full takeover of the device by using a simple reverse shell technique. After that, we access a file that\u2019s stored on the QNAP storage. Any file stored can be accessed similarly.\u201d\n\nQNAP said a fix for supported hardware can be downloaded from the QNAP App Center and is identified as Multimedia Console 1.3.4. See Also: Hacking Stories: When two young hackers played war games with PentagonQNAP Patch Timeline\u201cCurrently, we have released the fix in the latest firmware and related app,\u201d QNAP representatives told Threatpost. \u201cSince the severity level is high, we would like to release the security update for legacy versions. It is expected to be available in a week. In addition, we hope there will be another week for users\u2019 updates.\u201d\nSource: https://threatpost.com (Click Link)style=\"display:block\"\n data-ad-client=\"ca-pub-6620833063853657\"\n data-ad-slot=\"8337846400\"\n data-ad-format=\"auto\"\n data-full-width-responsive=\"true\"> Recent News* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/04/iphone-privacy-90x90.jpg Apple, Google Both Track Mobile Telemetry Data, Despite Users Opting Out1 day ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/Monero-Mining-90x90.png Malicious Docker Cryptomining Images Rack Up 20M Downloads2 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/phph-90x90.jpg PHP Infiltrated with Backdoor Malware3 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/ransomware_global_small-90x90.jpg Insurance Giant CNA Hit with Novel Ransomware Attack4 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/Microsoft-Teams-90x90.jpg Microsoft Offers Up To $30K For Teams Bugs1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/thrive-themes-1030x391-1-90x90.png Active Exploits Hit WordPress Sites Vulnerable to Thrive Themes Flaws1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/HL-color-90x90.jpg Hobby Lobby Exposes Customer Data in Cloud Misconfiguration1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/adobe_coldfusion-700x412-e1542041238507-90x90.jpg Adobe Fixes Critical ColdFusion Flaw in Emergency Update1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/Clubhouse-e1614022265127-90x90.jpg Bogus Android Clubhouse App Drops Credential-Swiping Malware2 weeks ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/apple-security-90x90.jpg Trojanized Xcode Project Slips MacOS Malware to Apple Developers2 weeks ago\nThe post Legacy QNAP NAS Devices Vulnerable to Zero-Day Attack first[...]", "creation_timestamp": "2026-09-02T01:03:25.465849Z"}, {"uuid": "90b8f0b2-a9c1-4d2e-a394-e75352453b4d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-36195", "type": "seen", "source": "https://t.me/hacking_Attack/3429", "content": "Black Hat Ethical Hacking\nLegacy QNAP NAS Devices Vulnerable to Zero-Day Attack\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Legacy QNAP NAS Devices Vulnerable to Zero-Day AttackPost Views: 63 \nstyle=\"display:block\"\n data-ad-client=\"ca-pub-6620833063853657\"\n data-ad-slot=\"8337846400\"\n data-ad-format=\"auto\"\n data-full-width-responsive=\"true\"> \nReading Time: 1 Minute\nTwo critical zero-day bugs affect legacy QNAP Systems storage hardware, and expose devices to remote unauthenticated attackers.\nThe bugs, tracked as CVE-2020-2509 and CVE-2021-36195, impact QNAP\u2019s model TS-231 network attached storage (NAS) hardware, allowing an attacker to manipulate stored data and hijack the device. The vulnerabilities, also impact some non-legacy QNAP NAS gear. However, it is important to note that patches are available for non-legacy QNAP NAS hardware.\n\nA patch for the now-retired QNAP model TS-231 NAS device, first released in 2015, is scheduled to be released within weeks, QNAP representatives told Threatpost.\n\nPatches for current model QNAP devices need to be downloaded from the QNAP download center and applied manually. Zero-Day DisclosureBoth bugs were disclosed on Wednesday by SAM Seamless Network researchers, who released limited technical details. The disclosure was ahead of official QNAP public disclosure of the vulnerabilities, and was in line with SAM Seamless Network\u2019s disclosure policy of giving a vendor three months to disclose vulnerability details. Both flaws were found in the Oct. and Nov. 2020 timeframe and made public Wednesday.\n\n\u201cWe reported both vulnerabilities to QNAP with a four-month grace period to fix them,\u201d researchers wrote. \u201cDue to the seriousness of the vulnerabilities, we decided not to disclose the full details yet, as we believe this could cause major harm to tens of thousands of QNAP devices exposed to the internet.\u201d\nSee Also: Apple, Google Both Track Mobile Telemetry Data, Despite Users Opting Out\nQNAP would not specifically say how many additional legacy NAS devices may be impacted. The company, in a statement to Threatpost said: \u201cThere are many hardware models of NAS in QNAP. (See: https://www.qnap.com/en/product/eol.php). In the list, you can find the models, the period of hardware repair or replacement, the supported OS and App updates and maintenance and the status of technical support and security updates. Most of the models, the security update could be upgraded to the latest version, i.e. QTS 4.5.2. However, some old hardware models have limits of firmware upgrade. For example, TS-EC1679U-SAS-RP could support only the legacy QTS 4.3.4.\u201d Breaking Down QNAP Bug OneTracked as CVE-2020-2509, this remote code execution (RCE) bug is tied to firmware used in both old and new hardware, according to QNAP. Firmware versions prior to QTS 4.5.2.1566 (build 20210202) and QTS 4.5.1.1495 (build 20201123) are affected. Patches for current (non-legacy) hardware can be downloaded via QTS 4.5.2.1566 (ZIP) and QTS 4.5.1.1495 (ZIP).\n\nThe bug (CVE-2020-2509) resides in the NAS web server (default TCP port 8080), according to researchers.\n\n\u201cPrevious RCE attacks on QNAP NAS models relied on web pages which do not require prior authentication, and run/trigger code in server-side. We\u2019ve therefore inspected some CGI files (which implement such pages) and fuzzed a few of the more relevant ones,\u201d researchers described.\n\nThey said that during the inspection, they were able to fuzz the web server with customized HTTP requests to different CGI pages, focusing on ones that didn\u2019t require prior authentication. \u201cWe\u2019ve been able to generate an interesting scenario, which triggers remote code execution indirectly (i.e[...]", "creation_timestamp": "2026-09-02T01:03:25.415796Z"}]}