Comparison Overview
RaSpect

RaSpect
133 Wai Yip St, Kwun Tong District, HK
Last Update: 01/04/2026
RaSpect is an innovative AI deep tech company focused on smart city solutions, specializing in safety and sustainability for smart buildings and infrastructure. They provide patented AI technology and SaaS solutions for facility management firms, property managers, engi...

Amdocs
1390 Timberlake Manor Parkway, Chesterfield, 63017, US
Last Update: 13/09/2026
Who are we? Amdocs helps those who build the future to make it amazing. With our market-leading portfolio of software products and services, we unlock our customers’ innovative potential, empowering them to provide next-generation communication and media experiences for...
Compliance Ranges Comparison

RaSpect







Amdocs






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for RaSpect in 2026.
Incidents vs Software Development Industry Avg (This Year)
Amdocs has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - RaSpect (X = Date, Y = Severity)
RaSpect cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amdocs (X = Date, Y = Severity)
Amdocs cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

RaSpect

Amdocs
FAQ
Latest Global CVEs
The web management service in affected RouterOS versions contains an integer underflow in its HTTP request body handling that is reachable before authentication. This can be leveraged by an unauthenticated network attacker to achieve arbitrary code execution as root, or to cause a denial of service, using a single crafted request.
Denuvo Anti-Tamper through 2026-03-04 allows bypass of a hypervisor presence check via CPUID interception (SimpleSvm.sys on AMD; hyperkd.sys and hyperhv.dll on Intel).
PeaZip before 11.3.0, in a non-default configuration, is vulnerable to OS command injection via a filename in an archive because "quotation character already used in the string" is mishandled.
Zilliz Attu before 3.0.0 has a Playground feature that does not require authentication for proxying arbitrary HTTP and HTTPS requests to URLs on the public internet.
The Playground feature of Zilliz Attu before 3.0.0 allows SSRF (proxying of requests to private IP addresses).