Comparison Overview
beOn Claro
beOn Claro
Rua Henri Dunant 780, São Paulo, SP, 04709-110, BR
Last Update: 05/12/2025
beOn é o hub de inovação da Claro que atua como uma Venture Builder dentro do modelo de inovação aberta. Selecionamos projetos e estabelecemos parcerias com startups em diferentes níveis de maturidade. Disponibilizamos a expertise de inovação e tecnologia do Grupo Claro...
stc
King Abdul Aziz Complex, Riyadh, SA
Last Update: 11/09/2026
We are a forward-focused digital champion always been focused on innovation and evolution. Our purpose is to create and bring greater dimension and richness to people’s personal and professional lives. With stc, You will always be empowered to focus on delivering w...
Compliance Ranges Comparison
beOn Claro
stc
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for beOn Claro in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for stc in 2026.
Incident History - beOn Claro (X = Date, Y = Severity)
beOn Claro cyber incidents detection timeline including parent company and subsidiaries.
Incident History - stc (X = Date, Y = Severity)
stc cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
beOn Claro
stc
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.