Comparison Overview
Cook Systems

Cook Systems
undefined, Nashville, Tennessee, undefined, US
Last Update: 22/03/2026
At Cook Systems, our 30-year legacy in the IT services industry and commitment to innovation drive our passion for developing exceptional IT talent. Serving numerous Fortune 500 clients from our Tennessee headquarters, our transformative approach sets us apart in the te...

Amazon Web Services (AWS)
410 Terry Ave N, Seattle, WA, US, 98019
Last Update: 07/06/2026
Launched in 2006, Amazon Web Services (AWS) began exposing key infrastructure services to businesses in the form of web services -- now widely known as cloud computing. The ultimate benefit of cloud computing, and AWS, is the ability to leverage a new business model and...
Compliance Ranges Comparison

Cook Systems







Amazon Web Services (AWS)






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Cook Systems in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Amazon Web Services (AWS) has 1184.4% more incidents than the average of all companies with at least one recorded incident.
Incident History - Cook Systems (X = Date, Y = Severity)
Cook Systems cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amazon Web Services (AWS) (X = Date, Y = Severity)
Amazon Web Services (AWS) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Cook Systems

Amazon Web Services (AWS)
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.