Comparison Overview
SVR Tracking
SVR Tracking
7170 Convoy Ct, San Diego, 92111, US
Last Update: 31/03/2026
3 year plans with NO MONTHLY FEES! SVR Tracking uses GPS to let you know where your vehicles are. With detailed reporting capabilities, you can manage and recover your vehicles, if necessary, resulting in a better business all around. SVR Tracking’s GPS tracking ...
Samsung SDS
Samsung SDS 125, Olympic-ro 35-gil, Songpa-gu, Seoul, 05510, KR
Last Update: 29/03/2026
Samsung SDS provides cloud computing and digital logistics services. We build an optimized cloud environment with Samsung Cloud Platform specialized for businesses, provide all-in-one management service based on 38 years of expertise in each industry, and boost work eff...
Compliance Ranges Comparison
SVR Tracking
Samsung SDS
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for SVR Tracking in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Samsung SDS in 2026.
Incident History - SVR Tracking (X = Date, Y = Severity)
SVR Tracking cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Samsung SDS (X = Date, Y = Severity)
Samsung SDS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SVR Tracking
Samsung SDS
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.