Comparison Overview
ST Engineering North America

ST Engineering North America
2011 Crystal Dr, Arlington, Virginia, US, 22202
Last Update: 31/12/2025
ST Engineering is a global technology, defense and engineering group with a diverse portfolio of businesses across the aerospace, smart city, defense and public security segments. In the U.S., we operate in over 50 cities across 21 states with our headquarters in Arlin...

Lockheed Martin
6801 Rockledge Drive, Bethesda, 20817, US
Last Update: 20/05/2026
The world relies on what we do. Headquartered in Bethesda, Maryland, with offices across the U.S. and around the globe, our team delivers solutions that strengthen national security, shape industries and push engineering and technology to new levels. We collaborate t...
Compliance Ranges Comparison

ST Engineering North America







Lockheed Martin






Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for ST Engineering North America in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
Lockheed Martin has 85.19% more incidents than the average of all companies with at least one recorded incident.
Incident History - ST Engineering North America (X = Date, Y = Severity)
ST Engineering North America cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lockheed Martin (X = Date, Y = Severity)
Lockheed Martin cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ST Engineering North America

Lockheed Martin
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.