CVE Vulnerabilities

CVE-2016-9155

Improper Access Control

Published: Nov 22, 2016 | Modified: Dec 23, 2016
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu

The following SIEMENS branded IP Camera Models CCMW3025, CVMW3025-IR, CFMW3025 prior to version 1.41_SP18_S1; CCPW3025, CCPW5025 prior to version 0.1.73_S1; CCMD3025-DN18 prior to version v1.394_S1; CCID1445-DN18, CCID1445-DN28, CCID1145-DN36, CFIS1425, CCIS1425, CFMS2025, CCMS2025, CVMS2025-IR, CFMW1025, CCMW1025 prior to version v2635_SP1 could allow an attacker with network access to the web server to obtain administrative credentials under certain circumstances.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Ccid1445-dn18_firmware Siemens - (including) - (including)
Ccid1445-dn28_firmware Siemens - (including) - (including)
Ccid1445-dn36_firmware Siemens - (including) - (including)
Ccis1425_firmware Siemens - (including) - (including)
Ccmd3025-dn18_firmware Siemens - (including) - (including)
Ccms2025_firmware Siemens - (including) - (including)
Ccmw1025_firmware Siemens - (including) - (including)
Ccmw3025_firmware Siemens - (including) - (including)
Ccpw3025_firmware Siemens - (including) - (including)
Cfis1425_firmware Siemens - (including) - (including)
Cfms2025_firmware Siemens - (including) - (including)
Cfmw1025_firmware Siemens - (including) - (including)
Cfmw3025_firmware Siemens - (including) - (including)
Cvms2025-ir_firmware Siemens - (including) - (including)
Cvmw3025-ir_firmware Siemens - (including) - (including)

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References