Comparison Overview
Naval Surface Warfare Center Dahlgren Division

Naval Surface Warfare Center Dahlgren Division
6149 Welsh Rd Suite 203, Dahlgren, VA, 22448, US
Last Update: 17/12/2025
The Naval Surface Warfare Center Dahlgren Division originally established itself as the major testing area for naval guns and ammunition. Today, it continues to provide the military with the development and integration of warfare systems for the warfighter, warfighting ...

US Navy
1200 Navy Pentagon, Washington, 20350, US
Last Update: 02/04/2026
The United States is a maritime nation, and the U.S. Navy protects America at sea. Alongside our allies and partners, we defend freedom, preserve economic prosperity, and keep the seas open and free. Our nation is engaged in long-term competition. To defend American int...
Compliance Ranges Comparison

Naval Surface Warfare Center Dahlgren Division







US Navy






Benchmark & Cyber Underwriting Signals
Incidents vs Armed Forces Industry Avg (This Year)
No incidents recorded for Naval Surface Warfare Center Dahlgren Division in 2026.
Incidents vs Armed Forces Industry Avg (This Year)
No incidents recorded for US Navy in 2026.
Incident History - Naval Surface Warfare Center Dahlgren Division (X = Date, Y = Severity)
Naval Surface Warfare Center Dahlgren Division cyber incidents detection timeline including parent company and subsidiaries.
Incident History - US Navy (X = Date, Y = Severity)
US Navy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Naval Surface Warfare Center Dahlgren Division

US Navy
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.