Summary
Brickcom network cameras expose live snapshot images through the /ONVIF endpoint without requiring authentication.
Anyone who can reach the camera over the network can retrieve still images from the video feed, potentially disclosing sensitive visual information and surveillance coverage.
Affected context
The vulnerability occurs in Brickcom IP camera deployments that expose the /ONVIF endpoint on a reachable network interface.
In affected configurations, the HTTP endpoint serving still images does not enforce any authentication or session validation.
This becomes particularly risky when cameras are accessible from untrusted networks, such as the broader corporate LAN, partner networks, or the public internet.
Exploit preconditions
- Attack surface: HTTP/ONVIF snapshot endpoint (
/ONVIF) on the camera. - Required access: Network-level connectivity to the camera's HTTP service (local network or internet, depending on deployment).
- Trigger point: An unauthenticated HTTP request to the snapshot URL to retrieve still images.
- Why exploitation is possible: The endpoint handling image capture and delivery fails to perform authentication or authorization checks before serving content, allowing any network client to access snapshots by direct request.
Why this happens
The core issue is a failure to enforce authentication on a sensitive operation, aligning with CWE-306: Missing Authentication for Critical Function.
The camera firmware exposes a feature that provides current video frame snapshots but does not require credentials or validate user identity.
This insecure pattern treats a privacy-sensitive capability—access to live surveillance imagery—as a public resource, instead of enforcing consistent authentication and access control across all camera data endpoints.
Potential impact
- Unauthorized viewing of live or near-live surveillance images from protected areas.
- Exposure of sensitive information such as personnel movements, security procedures, or asset locations.
- Assistance to physical intruders in planning routes, timing, and blind spots around monitored facilities.
- Privacy violations impacting employees, customers, or residents captured by the cameras.
- Reputational damage and potential regulatory non-compliance where video data is considered personal or sensitive information.
General mitigation guidance
Mitigation typically centers on enforcing strong, consistent authentication and reducing unnecessary exposure of camera interfaces.
Common defensive patterns include:
- Requiring authentication for all endpoints that provide access to images, video streams, or configuration data.
- Applying a single, centralized access control layer for HTTP/ONVIF services so no path bypasses authentication.
- Segmenting camera networks so that video endpoints are only reachable from trusted management networks or VPNs.
- Enforcing least privilege for viewing permissions, separating viewer, operator, and admin roles where supported.
- Using secure defaults: disabling anonymous access, disabling unneeded services, and requiring credential setup at initial configuration.
How teams detect issues like this
Organizations can identify similar issues using a combination of technical and process-based approaches:
- Network scanning and HTTP inspection to detect camera endpoints that return snapshots or streams without authentication.
- Manual and automated security testing of camera web interfaces, verifying that all media and configuration URLs enforce login.
- Configuration audits comparing deployed camera settings against baseline policies for authentication and network segmentation.
- Static or firmware-focused analysis to review web handlers and ONVIF services for missing authentication checks.
- Integration of these checks into procurement and onboarding processes, requiring security validation for new device types.

