Comparison Overview
Central - Future Lifestyle Fashion Limited

Central - Future Lifestyle Fashion Limited
Future Retail Home Office, Tower C, 247 Park, , Mumbai, Maharashtra, 400083, IN
Last Update: 16/12/2025
Central was launched in May 2004 in Bangalore, as India's first seamless store and the biggest lifestyle retail brand from Future Group. Central offers discerning shoppers options of choosing from over 1000 best brands across categories including apparels, cosmetics, fr...

SQ Group
Concord IK Tower, Level 4, North Avenue, Gulshan 2 Dhaka, Dhaka 1212, BD
Last Update: 29/03/2026
Q Collection, based in Singapore, is the parent company of the manufacturing entities collectively known as SQ Group in Bangladesh. As a leading global apparel manufacturing conglomerate, SQ is driven by a passion for innovation, sustainability, and excellence. With a r...
Compliance Ranges Comparison

Central - Future Lifestyle Fashion Limited







SQ Group






Benchmark & Cyber Underwriting Signals
Incidents vs Apparel & Fashion Industry Avg (This Year)
No incidents recorded for Central - Future Lifestyle Fashion Limited in 2026.
Incidents vs Apparel & Fashion Industry Avg (This Year)
No incidents recorded for SQ Group in 2026.
Incident History - Central - Future Lifestyle Fashion Limited (X = Date, Y = Severity)
Central - Future Lifestyle Fashion Limited cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SQ Group (X = Date, Y = Severity)
SQ Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Central - Future Lifestyle Fashion Limited

SQ Group
FAQ
Latest Global CVEs
An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command
The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.
An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS. Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.
The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.
An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.