Comparison Overview
TD SYNNEX DACH
TD SYNNEX DACH
Kistlerhofstraße 75, Munich, 81379, DE
Last Update: 02/12/2025
TD SYNNEX (NYSE: SNX) ist ein weltweit führender Distributor und Lösungsaggregator für das IT-Ecosystem. Wir sind ein innovativer Partner, der mehr als 150.000 Kunden in über 100 Ländern dabei hilft, den Wert von Technologieinvestitionen zu maximieren, Geschäftsergebnis...
Oracle
2300 Oracle Way, Austin, 78741, US
Last Update: 12/09/2026
Oracle is a global leader in AI, delivering the cloud infrastructure, data, and applications that organizations across the world trust to successfully achieve business outcomes at scale. Oracle Cloud Infrastructure (OCI) provides fast, flexible, scalable AI infrastruct...
Compliance Ranges Comparison
TD SYNNEX DACH
Oracle
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for TD SYNNEX DACH in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Oracle has 3006.8% more incidents than the average of all companies with at least one recorded incident.
Incident History - TD SYNNEX DACH (X = Date, Y = Severity)
TD SYNNEX DACH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Oracle (X = Date, Y = Severity)
Oracle cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
TD SYNNEX DACH
Oracle
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.