Comparison Overview
AREA 23 on Hudson | An IPG Health Company

AREA 23 on Hudson | An IPG Health Company
N/A
Last Update: 16/01/2026
AREA 23 on Hudson, an IPG Health Company, is a team of creative problem-solvers who don’t believe in a cookie-cutter approach to medical communications. Driven by a shared vision with our client partners, we innovate solutions to create lasting impact with HCPs. We do...

Teva Pharmaceuticals
124 Dvora hanevi'a, Tel-Aviv, IL, 6944020
Last Update: 28/03/2026
Teva Pharmaceuticals is a leading innovative biopharmaceutical company, enabled by a world-class generics business. For over 120 years, Teva’s commitment has never wavered. From innovating in the fields of neuroscience and immunology to providing complex generic medicin...
Compliance Ranges Comparison

AREA 23 on Hudson | An IPG Health Company







Teva Pharmaceuticals






Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for AREA 23 on Hudson | An IPG Health Company in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Teva Pharmaceuticals in 2026.
Incident History - AREA 23 on Hudson | An IPG Health Company (X = Date, Y = Severity)
AREA 23 on Hudson | An IPG Health Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Teva Pharmaceuticals (X = Date, Y = Severity)
Teva Pharmaceuticals cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

AREA 23 on Hudson | An IPG Health Company

Teva Pharmaceuticals
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.