Comparison Overview
Aster Pharmacy (India)

Aster Pharmacy (India)
28, PID No. 77-1-28, Ward No. 77, P. Kalinga Rao Road, Bengaluru, 560027, IN
Last Update: 21/03/2026
Aster Pharmacy is one of the largest retail pharmacy groups in the Middle East and is now present in India. We opened India's 1st friendly neighbourhood pharmacy in February 2021 and are rapidly expanding. With 3 decades of experience in the health care industry, we a...

Amplifon
Via Ripamonti 133, Milan, 20141, IT
Last Update: 31/03/2026
As the global leader in the hearing care retail industry, we have been changing the lives of millions of customers across the globe since 1950. With stores and offices spanning across 26 countries and a team of 20,300 dedicated professionals, we take pride in setting th...
Compliance Ranges Comparison

Aster Pharmacy (India)







Amplifon






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Health and Personal Care Products Industry Avg (This Year)
No incidents recorded for Aster Pharmacy (India) in 2026.
Incidents vs Retail Health and Personal Care Products Industry Avg (This Year)
No incidents recorded for Amplifon in 2026.
Incident History - Aster Pharmacy (India) (X = Date, Y = Severity)
Aster Pharmacy (India) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amplifon (X = Date, Y = Severity)
Amplifon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Aster Pharmacy (India)

Amplifon
FAQ
Latest Global CVEs
A vulnerability was determined in xuxueli xxl-job up to 3.5.0. The impacted element is an unknown function of the file /jobgroup/insert. This manipulation of the argument Name causes cross site scripting. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
A vulnerability was found in Moore Threads MTT S80 Driver Package 340.150. The affected element is the function sub_140006F0C in the library mtdispkm64.sys of the component IOCTL Handler. The manipulation results in improper privilege management. Attacking locally is a requirement. The vendor was contacted early about this disclosure but did not respond in any way.
vLLM Mooncake connector through 0.29.0 fails to properly manage GPU KV cache block ownership when concurrent child requests share a single transfer ID in prefill/decode disaggregated deployments. Attackers can trigger GPU memory exhaustion by submitting completion requests with multiple prompts, causing orphaned KV cache blocks to accumulate until process restart and eventually preventing legitimate requests from executing.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/mooncake/mooncake_connector.py#L1978-L1989
- https://github.com/vllm-project/vllm/pull/49796
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-gpu-kv-cache-leak-via-mooncake-transfer-id-collision
vLLM through 0.29.0 fails to validate the tp_size parameter in kv_transfer_params on OpenAI-compatible completion endpoints, allowing attackers to allocate unbounded memory. Attackers can supply arbitrary tp_size values in prefill/decode disaggregated deployments to exhaust memory and trigger kernel OOM-kill of the decode worker process.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/utils.py#L569-L573
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/metadata.py#L277
- https://github.com/vllm-project/vllm/pull/51137
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-unvalidated-nixl-tp-size
vLLM through 0.29.0 contains a resource exhaustion vulnerability in MooncakeConnector where rejected prefill requests create ownerless transfer placeholders that are never reclaimed. Attackers can send rejected requests to exhaust sender task pools, causing valid requests to be delayed by up to 480 seconds while health checks continue returning success.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/mooncake/mooncake_connector.py#L1234-L1242
- https://github.com/vllm-project/vllm/pull/51236
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-resource-exhaustion-via-ownerless-mooncake-transfer-placeholders