Comparison Overview
Dolby Laboratories

Dolby Laboratories
1275 Market St, San Francisco, California, US, 94103
Last Update: 29/04/2026
We're the rain on the roof in a movie. The music flowing through your earbuds when you're at the gym. The footsteps lurking behind you in a video game. The voice of a colleague on a call who seems to be right next to you. The sight of a breathtakingly bright and vivid s...

Canon USA
One Canon Park, Melville, NY, US, 11747
Last Update: 03/04/2026
Living and Working Together For The Common Good... - Kyosei Kyosei unites Canon and its employees in contributing to the prosperity of humanity and the protection of the world we share. As a leading provider of consumer, business-to-business, and industrial digital ...
Compliance Ranges Comparison

Dolby Laboratories







Canon USA






Benchmark & Cyber Underwriting Signals
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
Dolby Laboratories has 17.65% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Canon USA in 2026.
Incident History - Dolby Laboratories (X = Date, Y = Severity)
Dolby Laboratories cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Canon USA (X = Date, Y = Severity)
Canon USA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Dolby Laboratories

Canon USA
FAQ
Latest Global CVEs
In OpenStack Designate before 22.0.2, the mDNS handler performs pool-blind lookups when resolving record queries and NOTIFY requests. When two zones with the same name exist across different pools, the lookup fails with a deterministic error, causing the handler to return REFUSED for all DNS queries through that path. The _handle_notify path is exploitable via a single unauthenticated UDP packet. This is independently reachable through the cross-tenant zone overlap described in a different recent CVE, and also affects legitimate same-tenant cross-pool configurations. BIND9 views do not mitigate this issue as mDNS is a shared service upstream of any view configuration.
In OpenStack Designate before 22.0.1, zone creation checks (_is_subzone, _is_superzone, and the duplicate-zone DB constraint) are scoped to the target pool only. An authenticated user can bypass these checks by scheduling a zone to a different pool via the AttributeFilter scheduler, creating an overlapping zone that conflicts with another tenant's zone. This enables cross-tenant DNS hijack (redirecting traffic to attacker-controlled IPs) and DNS denial of service (NODATA responses). Exploitation requires a multi-pool deployment with AttributeFilter enabled in scheduler_filters, which is a non-default but documented and supported configuration for self-service tiering.
UpSnap is a wake on lan web app. Versions prior to 5.4.0 have an OS command injection vulnerability in the UpSnap’s device management functionality due to the presence of unsafe shell command template interpolation using the ip and the mac fields. User-controlled values can be inserted into the wake_cmd and shutdown_cmd templates and executed via /bin/sh -c (Linux) or cmd /C (Windows) without sanitization, resulting in an authenticated Remote Code Execution (RCE). A low-privileged user with permission to create or edit devices can execute arbitrary operating system commands on the UpSnap hosted server. Version 5.4.0 patches the issue.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. When `secureEnabled=true`, FUXA `1.3.0-2773` still allows guest and invalid-token requests to read project, alarms, and scheduler APIs. Version 1.3.1 fixes this issue.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. In fuxa-server version 1.3.0, the GET /api/project endpoint exposes sensitive project configuration data to guest-context requests even when secureEnabled is enabled. Version 1.3.1 fixes the issue.