Comparison Overview
Bata Malaysia

Bata Malaysia
B-17, Menara Bata, No. 8, Jalan PJU 8/8A,, Petaling Jaya, 47820, MY
Last Update: 30/01/2026
At Bata Malaysia, we’re more than just a footwear brand — we’re a part of your journey. From everyday essentials to festive collections, our designs are made with comfort, style, and the Malaysian spirit in mind. With over 130 years of global heritage and a strong loca...

J.Crew
225 Liberty St, New York, New York, US, 10281
Last Update: 29/03/2026
Since 1983, we’ve been designing pieces that feel both familiar and refreshingly new, crafted with unbeatable quality and distinctive point of view...it’s no wonder we’ve been in your closet for four decades and counting. Today, we continue to do the classics our way, ...
Compliance Ranges Comparison

Bata Malaysia







J.Crew






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Bata Malaysia in 2026.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for J.Crew in 2026.
Incident History - Bata Malaysia (X = Date, Y = Severity)
Bata Malaysia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - J.Crew (X = Date, Y = Severity)
J.Crew cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bata Malaysia

J.Crew
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.