Comparison Overview
CuraScript SD by Evernorth

CuraScript SD by Evernorth
255 Technology Park, Lake Mary, 32746, US
Last Update: 25/02/2026
More than a specialty distributor At our core, CuraScript SD provides integrated delivery solutions for the safe and efficient distribution of specialty pharmaceuticals and associated medical supplies. We’ve been caring for those who care for more than a quarter of a ce...

Cipla
Lower Parel, Ganpatrao Kadam Marg,, Mumbai, Maharashtra, IN, 400013
Last Update: 01/04/2026
Cipla is a leading global pharmaceutical company trusted by healthcare professionals and patients across the world since 1935. A compassionate approach to healthcare that goes beyond the pursuit of profit and growth has been the force impelling Cipla’s history over the ...
Compliance Ranges Comparison

CuraScript SD by Evernorth







Cipla






Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for CuraScript SD by Evernorth in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Cipla in 2026.
Incident History - CuraScript SD by Evernorth (X = Date, Y = Severity)
CuraScript SD by Evernorth cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cipla (X = Date, Y = Severity)
Cipla cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CuraScript SD by Evernorth

Cipla
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.