Comparison Overview
Norfolk Naval Shipyard

Norfolk Naval Shipyard
None, None, Portsmouth, VA, US, 23709
Last Update: 19/03/2026
"We are America's Shipyard" We are Norfolk Naval Shipyard (NNSY), continuously driving to excellence and delivering service to the fleet safely with the right quality on schedule and within budget. NNSY is recognized as a world class organization in executing our missi...

General Dynamics
11011 Sunset Hills Rd, Reston, 20190, US
Last Update: 01/04/2026
From Gulfstream business jets and combat vehicles to nuclear-powered submarines and communications systems, people around the world depend on our products and services for their safety and security. General Dynamics is headquartered in Reston, Virginia, and employs ove...
Compliance Ranges Comparison

Norfolk Naval Shipyard







General Dynamics






Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Norfolk Naval Shipyard in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
General Dynamics has 7.41% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Norfolk Naval Shipyard (X = Date, Y = Severity)
Norfolk Naval Shipyard cyber incidents detection timeline including parent company and subsidiaries.
Incident History - General Dynamics (X = Date, Y = Severity)
General Dynamics cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Norfolk Naval Shipyard

General Dynamics
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.