Brickcom Cameras
MonitorCVSS 7.7ICS-CERT ICSA-26-162-03Jun 11, 2026
Attack path
Attack VectorLocal
Auth RequiredNone
ComplexityLow
User InteractionNone needed
Summary
Brickcom Cube, Dome, Bullet, and Box cameras version 3.2.3.5.6 contain authentication and access control vulnerabilities (CWE-306, CWE-1392) that allow remote unauthenticated attackers to gain unauthorized access to live video feeds and obtain administrative control of the device. Successful exploitation could allow unauthorized viewing of sensitive visual information and full device compromise.
What this means
What could happen
An unauthenticated attacker with local access to the network could view live video feeds and gain administrative control of the camera, potentially allowing them to disable surveillance, alter recordings, or use the compromised device as an entry point to other network systems.
Who's at risk
Water and utility operators who rely on Brickcom network cameras (Cube, Dome, Bullet, or Box models) for perimeter monitoring, facility surveillance, or process oversight. This affects any organization using these cameras in version 3.2.3.5.6.
How it could be exploited
An attacker on the same local network (or with network access to the camera) could connect to the camera without providing credentials and exploit the missing authentication controls to access the web interface or management functions, then gain full administrative privileges.
Prerequisites
- Network access to the camera (same subnet or routable path)
- Camera running vulnerable firmware version 3.2.3.5.6 or earlier
no authentication requiredlow complexityaffects surveillance systemsno patch availablevendor non-responsive
Exploitability
Unlikely to be exploited — EPSS score 0.2%
Affected products (4)
4 pending
ProductAffected VersionsFix Status
Brickcom Cube: 3.2.3.5.63.2.3.5.6No fix yet
Brickcom Dome: 3.2.3.5.63.2.3.5.6No fix yet
Brickcom Bullet: 3.2.3.5.63.2.3.5.6No fix yet
Brickcom Box: 3.2.3.5.63.2.3.5.6No fix yet
Remediation & Mitigation
0/3
Do now
0/1WORKAROUNDRestrict network access to the cameras by implementing firewall rules to allow connections only from authorized engineering and monitoring workstations
Schedule — requires maintenance window
0/1Patching may require device reboot — plan for process interruption
HOTFIXContact Brickcom support directly at https://www.brickcom.com/case/ to request a firmware update that addresses the authentication vulnerabilities
Long-term hardening
0/1HARDENINGSegment cameras onto a dedicated VLAN separate from critical control systems and corporate networks
CVEs (2)
↑↓ Navigate · Esc Close
API:
/api/v1/advisories/b395aecc-50c1-4b1c-9cfa-770f69b68047Get OT security insights every Tuesday
Advisory breakdowns, a weekly summary, and incident analyses for the people actually defending OT environments. Free, no account required.