QNAP Major Security Bug

By Sarit Williams, Published Jun 10, 2013, 12:00am EDT (Info+)

QNAP, a manufacturer of Linux embedded NVRs and Network Attached Storage (NAS) solutions have ignored a colossal security bug. This article will delve into the sheer negligence and the high level of risk that has been transferred to their customers to bear unwillingly, in addition to discussing the vulnerabilities' ratings.

What Happened

*** **** ********* ******** ********* ***, ***** ******* *************** **** ****’******** *********** ******* *.*.* (*** ******** ******* versions).

  • **** **** ***** * ***** ******* **** *** be ********* ** ****** ***** ************* level ********. **** ***** ******* ***** then **** ********* ****** ** *** NVR. ********, *** ***** ******* ****** cannot ** *********** ** ******** ** there's ** *** ** **** **** this *********.
  • ** ******** ***** ***** ******, ** attacker *** ****** ****** *** ******. **** if *** **** ** *** * programmer, **** ***** ************* ****** * ****-***** changing *** ******* ****** ** *** script *** ******** ******** *****.
  • **** ** ******** *** ******** * server, **** *** ***** ***** (**** the *** ***********) **** ********** ********* data ** *************** ******** ** **** the ******** ****** ** ******.

***** ***** *** ********** ****** ** expose *** *********** ************ ** *** NVR *** ****** **** ********** ** use **.

******* ****** ******** ** ******* **** personnel ****** *** ******** ******* ** report *** *********** ** *** ******** Engineering *********, ****, ** ***** ** **** *** then ** ***** ******** ******* [**** ** longer *********]****** *** * ********.

QNAP ********

* ****** ***** ** *** ******** disclosed **** ******* ********* **** ****** ** *** *** *************

Highest **** *****

*** ******** ************* ******** (***) ***** ***** *************** ** **** score ** ** – ***** ******* vulnerability ** *** ****** ************* ******* System (****).  *** ***** **********:***-***,***-**, ******-************* *** ******’* ******** *** **** range ** ******** *** ***** **** in *** *** *******.

*** ****** ***** *** ******** *** executed *** **** *** **** ** identifying *** *******, ******** ******** ***** servers *** ******* ************. ***********, ****** a ‘******’ ****** *** ****** *** NVR’s *********, ** ****** ****** *** link’s **** ** *** ******* *** leave *** **** ********* (**) ** the *********** ** *** ******** ****.

****'* * **** ***** ** ***** **** Request *******:

*** ****'* ***** ******** ***** *************** *** **** ****.

What ** ***** ** ***

****** *** **** ******* ***********. *** attack ** ****** ****** *** ********* on *** ********. *** ******** *** attain ******** ******* **** *** *** application - ******** ** ******** *****,********* **** ******* ** ******* ** the *******, ****** ******* **** *** ********’* features **** ** *** **** ********* every *** ************ *** ************ *** just **** ********, *** ******* *** ability ** ****** *** **********’ ********* and ******** ** ****.   

Linux *****?

***** **** *** ** ***** **** a ***** *********, **** *** *** a ***** ** *****. **** ******* made * **** ***** ******* ** setting ** ***** *** ******. 

*** ********* ** *** ****** **** *** ***** ******** **************; it ** ****** * ******* ** exploiting *** ******’* ******** *** ***** left ** *** *******. ***** *** ****** integration ******* *** ****** ******* ********* (***) *********. **** ****** **** ********, resides ** *** ****** ** ***** scripts *** *********** ******** ** *** application ** ******** *** ******** **** the ****** ** *** ****** ** process **** *******; ******* ****** ****** authentication ** ********.

**********

******** ********* *** ***** ** *****-******* testing ********* *** **** ******* ** a ***** ***. ** **** ****, it *** ********** * ******* ** architecture *** ****** **** ********** ***** issues ** ****’* **********. *** *** say ** *** ** *********, ***** is ******* ******* ** ***** **** of ******** ** *** ******* - and **** **** ******** ********** *** several **** ******. ************, ****** *** architecture *** *** ***** ******** ****** of *** *********** *** ***** *********** flaws **** ******* * ******** ** the *********** ** * ***** ** address ***** ****** **********.

** ******* ******* *************** *****, ********* ** **** ******** security ********* *** ****** ******.

 

****** (*/**/****):**** *** ******** *** ********* updates *** **** ********** *******:

**** ******* *** ******** ******* *.*.* and ******** ******* ******** ***** *** advised ** ******* ** **** ******* NVR ****** ******** ******* *.*.* ***** 6612.


**** *** **** *** ************ ******* Pro ********* *** ******* ** ******* to **** ************ ******* *** ** v3.0.2 ** ******.

Login to read this IPVM report.
Why do I need to log in?
IPVM conducts reporting, tutorials and software funded by subscriber's payments enabling us to offer the most independent, accurate and in-depth information.
Loading Related Reports