Comparison Overview
Beiersdorf Dermo Medical GmbH

Beiersdorf Dermo Medical GmbH
Unnastraße 48, Hamburg, 20253, DE
Last Update: 01/04/2026
Seit über 140 Jahren steht der Name Beiersdorf für innovative Hautpflege. Der Erfolg unseres Unternehmens begründet sich seit jeher durch die starke Innovationskraft und die enge Verbindung von Forschung, dermatologischem Fachwissen und der konsequenten Weiterentwicklun...

Natura
Av. Alexandre Colares, 1.188, Vila Jaguara, São Paulo, São Paulo, BR, 05106-0000
Last Update: 28/03/2026
Founded in 1969, Natura is a Brazilian multinational in the cosmetics and personal care segment, a leader in direct sales in Brazil, and recognized for protecting the Amazon social biodiversity through its sustainable business model. Cruelty free. 100% vegan. With 7,000...
Compliance Ranges Comparison

Beiersdorf Dermo Medical GmbH







Natura






Benchmark & Cyber Underwriting Signals
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Beiersdorf Dermo Medical GmbH in 2026.
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Natura in 2026.
Incident History - Beiersdorf Dermo Medical GmbH (X = Date, Y = Severity)
Beiersdorf Dermo Medical GmbH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Natura (X = Date, Y = Severity)
Natura cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Beiersdorf Dermo Medical GmbH

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