First published: Wed Aug 31 2016(Updated: )
NUUO NVRmini 2 1.7.5 through 3.0.0, NUUO NVRsolo 1.0.0 through 3.0.0, and NETGEAR ReadyNAS Surveillance 1.1.1 through 1.4.1 have a hardcoded qwe23622260 password for the nuuoeng account, which allows remote attackers to obtain sensitive information via an __nvr_status___.php request.
Credit: cret@cert.org
Affected Software | Affected Version | How to fix |
---|---|---|
NETGEAR ReadyNAS Surveillance | =1.1.1 | |
NETGEAR ReadyNAS Surveillance | =1.1.2 | |
NETGEAR ReadyNAS Surveillance | =1.2.0.4 | |
NETGEAR ReadyNAS Surveillance | =1.3.2.4 | |
NETGEAR ReadyNAS Surveillance | =1.3.2.14 | |
NETGEAR ReadyNAS Surveillance | =1.4.0 | |
NETGEAR ReadyNAS Surveillance | =1.4.1 | |
NETGEAR ReadyNAS Surveillance | =1.4.2 | |
NUUO NVRmini 2 | =1.7.5 | |
NUUO NVRmini 2 | =1.7.6 | |
NUUO NVRmini 2 | =2.0.0 | |
NUUO NVRmini 2 | =2.2.1 | |
NUUO NVRmini 2 | =3.0.0 | |
NUUO NVRsolo | =1.0.0 | |
NUUO NVRsolo | =1.0.1 | |
NUUO NVRsolo | =1.1.0 | |
NUUO NVRsolo | =1.1.0.117 | |
NUUO NVRsolo | =1.1.1 | |
NUUO NVRsolo | =1.1.2 | |
NUUO NVRsolo | =1.2.0 | |
NUUO NVRsolo | =1.3.0 | |
NUUO NVRsolo | =1.75 | |
NUUO NVRsolo | =2.0.0 | |
NUUO NVRsolo | =2.0.1 | |
NUUO NVRsolo | =2.1.5 | |
NUUO NVRsolo | =2.2.2 | |
NUUO NVRsolo | =2.3 | |
NUUO NVRsolo | =2.3.1.20 | |
NUUO NVRsolo | =2.3.7.9 | |
NUUO NVRsolo | =2.3.7.10 | |
NUUO NVRsolo | =2.3.9.6 | |
NUUO NVRsolo | =3.0.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-5677 has a high severity rating due to the use of a hardcoded password that allows unauthorized remote access.
To fix CVE-2016-5677, update your NUUO NVRmini, NUUO NVRsolo, or NETGEAR ReadyNAS Surveillance to the latest firmware version that removes the hardcoded password.
CVE-2016-5677 affects NUUO NVRmini 2 versions 1.7.5 to 3.0.0, NUUO NVRsolo versions 1.0.0 to 3.0.0, and NETGEAR ReadyNAS Surveillance versions 1.1.1 to 1.4.1.
CVE-2016-5677 allows remote attackers to obtain sensitive information and potentially compromise the system.
There is no official workaround for CVE-2016-5677; the best mitigation is to upgrade the affected systems to secure versions.