Comparison Overview
Trauson Medical Instruments

Trauson Medical Instruments
Changzhou, CN
Last Update: 04/04/2026
Trauson, as a Stryker branch company, is located in Wujing High-tech Industrial Zone, Changzhou, Jiangsu. Trauson was established in 1986, is one of the pioneering enterprises in China’s orthopaedic industry, and one of the leading manufacturers of trauma products and ...

BD
1 Becton Drive, Franklin Lakes, 07417, US
Last Update: 01/04/2026
BD is one of the largest global medical technology companies in the world and is advancing the world of health™ by improving medical discovery, diagnostics and the delivery of care. The company supports the heroes on the frontlines of health care by developing innovativ...
Compliance Ranges Comparison

Trauson Medical Instruments







BD






Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Trauson Medical Instruments in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for BD in 2026.
Incident History - Trauson Medical Instruments (X = Date, Y = Severity)
Trauson Medical Instruments cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BD (X = Date, Y = Severity)
BD cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Trauson Medical Instruments

BD
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.