Comparison Overview
1O1O Corporate Solutions
1O1O Corporate Solutions
PCCW Tower, Hong Kong, Hong Kong Hong Kong, CN
Last Update: 08/05/2026
1O1O is dedicated to empowering the digital transformation of enterprises with end-to-end integrated mobile solutions employing emerging technologies, such as 5G, Internet of Thing (IoT) and Artificial Intelligence (AI). As the forerunner in network and mobility soluti...
Ooredoo Group
100 West Bay, Doha, Doha, QA, Po Box 217
Last Update: 05/09/2026
We are an award-winning international communications company operating across the Middle East, North Africa and Southeast Asia. Serving consumers and businesses in 10 countries, we deliver a leading data experience through a broad range of content and services via ...
Compliance Ranges Comparison
1O1O Corporate Solutions
Ooredoo Group
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for 1O1O Corporate Solutions in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Ooredoo Group in 2026.
Incident History - 1O1O Corporate Solutions (X = Date, Y = Severity)
1O1O Corporate Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ooredoo Group (X = Date, Y = Severity)
Ooredoo Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
1O1O Corporate Solutions
Ooredoo Group
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.