Comparison Overview
Polyak Eynez Enerji Üretim Madencilik San. ve Tic. A.Ş.

Polyak Eynez Enerji Üretim Madencilik San. ve Tic. A.Ş.
Elmadere Mahallesi Karaçam Küme Evleri No:14, İzmir, 35990, TR
Last Update: 29/04/2026
Polyak Eynez 2014 yılında kurulmuştur. Soma Linyit havzasında bulunan ruhsat alanında faaliyet gösteren şirketimiz, İzmir’in Kınık ilçesinin sınırları içinde bulunmaktadır. Türkiye’nin en derin ve en teknolojik yer altı linyit madeni olma özelliklerini taşıyan Kınık Li...

Jindal Steel Ltd.
Jindal Centre, 12, Bhikaiji Cama Place, Delhi, New Delhi, IN, 110066
Last Update: 25/05/2026
Jindal Steel is one of India’s foremost integrated steel producers, renowned for its scale, efficiency, and commitment to excellence. Operating on a robust mine-to-metal model, the Company leverages captive resources, advanced manufacturing capabilities, and a global di...
Compliance Ranges Comparison

Polyak Eynez Enerji Üretim Madencilik San. ve Tic. A.Ş.







Jindal Steel Ltd.






Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Polyak Eynez Enerji Üretim Madencilik San. ve Tic. A.Ş. in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Jindal Steel Ltd. in 2026.
Incident History - Polyak Eynez Enerji Üretim Madencilik San. ve Tic. A.Ş. (X = Date, Y = Severity)
Polyak Eynez Enerji Üretim Madencilik San. ve Tic. A.Ş. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Jindal Steel Ltd. (X = Date, Y = Severity)
Jindal Steel Ltd. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Polyak Eynez Enerji Üretim Madencilik San. ve Tic. A.Ş.

Jindal Steel Ltd.
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.