Comparison Overview
Hero Cosmetics
Hero Cosmetics
New York, 10013, US
Last Update: 09/03/2026
We started Hero Cosmetics with one goal — to create solutions-oriented products that can be a "hero" product when your skin is in a pinch. Our approach is simple — be mindful of the ingredients we use and avoid ingredients like parabens, alcohol and sulfates, be gentl...
O Boticário
Av. Rui Barbosa, 4.110, Parque das Fontes,, São José dos Pinhais, 83.050-010, BR
Last Update: 15/09/2026
A beleza transforma, encanta, conquista e também pode ser conquistada. Eis o ideal de beleza que O Boticário multiplica com seus produtos, lojas e em sua relação com o público. Desde 1977, O Boticário soma inspiração, ousadia, inovação e qualidade, despertando o respei...
Compliance Ranges Comparison
Hero Cosmetics
O Boticário
Benchmark & Cyber Underwriting Signals
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Hero Cosmetics in 2026.
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for O Boticário in 2026.
Incident History - Hero Cosmetics (X = Date, Y = Severity)
Hero Cosmetics cyber incidents detection timeline including parent company and subsidiaries.
Incident History - O Boticário (X = Date, Y = Severity)
O Boticário cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hero Cosmetics
O Boticário
FAQ
Latest Global CVEs
A flaw was found in nfs-utils. An unauthenticated remote attacker can trigger a Denial of Service (DoS) by sending repeated state notification requests to an exposed rpc.statd service. The service fails to properly release memory allocated during callback processing, leading to continuous memory growth. Sustained requests can exhaust system resources, eventually causing the service to degrade or crash.
A flaw was found in parted. A heap-based buffer overflow exists in libparted's file system resizing logic when handling FAT16 volumes. By convincing a user or administrator to resize a specially crafted FAT16 file system image with malformed directory metadata, an attacker can trigger an oversized read into a fixed-size memory buffer. This issue causes memory corruption, resulting in an application crash and a denial of service (DoS).
A flaw was found in parted. A heap-based buffer overflow can occur when processing a specially crafted FAT32 filesystem due to an integer calculation error during buffer allocation. A local attacker could exploit this by enticing a user or automated service to open a malicious filesystem image, resulting in an application crash leading to a Denial of Service (DoS) or potential memory corruption.
A flaw was found in libarchive. An attacker can cause a Denial of Service (DoS) or potential information disclosure due to a use-after-free vulnerability, which occurs when a program reads memory that has already been released. This issue arises when the archive_entry_copy_mac_metadata() function deallocates an internal buffer before completing a data copy. An attacker who can supply input to an application utilizing this function can trigger the flaw to crash the application or read uninitialized memory data.
A flaw was found in Nautilus. When a removable drive or disk image is unmounted or ejected, Nautilus prompts the user to empty the trash without verifying whether the trash directory paths are symbolic links. An attacker can exploit this flaw by tricking a user into mounting a crafted storage volume and confirming the prompt to empty the trash, leading to the arbitrary deletion of files accessible to that user.