Comparison Overview
Central Compensation Office CCO
Central Compensation Office CCO
Avenue Edmond-Vaucher 18, Genève, GE, 1211, CH
Last Update: 03/12/2025
The Central Compensation Office CCO is the Confederation's central implementing body for first-pillar social security, which covers: > old-age and survivors' insurance OASI > disability insurance DI > compensation for loss of earnings APG The CCO's mission is to implem...
Etat de Vaud
Rue Caroline 4, Lausanne, 1014, CH
Last Update: 31/03/2026
Le canton de Vaud, c’est plus de 800 000 personnes vivant dans plus de 300 communes ! Rejoindre l’Administration cantonale vaudoise, c’est s’engager aux côtés de près de 40’000 personnes unies dans un même but : servir la population. Pourquoi nous suivre ? Dédiez vot...
Compliance Ranges Comparison
Central Compensation Office CCO
Etat de Vaud
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Central Compensation Office CCO in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Etat de Vaud in 2026.
Incident History - Central Compensation Office CCO (X = Date, Y = Severity)
Central Compensation Office CCO cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Etat de Vaud (X = Date, Y = Severity)
Etat de Vaud cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Central Compensation Office CCO
Etat de Vaud
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.