Comparison Overview
Technology Commercialization Office of the George Washington University
Technology Commercialization Office of the George Washington University
1922 F ST NW, 4TH FL, Washington, DC, 20052, US
Last Update: 24/02/2026
The George Washington University (GW) Technology Commercialization Office (TCO), promotes and facilitates the transfer of GW innovations for the benefit of the university community and the public while leveraging GW resources by partnering with industry experts and entr...
RMIT University
124 La Trobe St, Melbourne, 3000, AU
Last Update: 01/04/2026
RMIT is a global university of technology, design and enterprise. One of Australia's original tertiary institutions, RMIT University enjoys an international reputation for excellence in professional and vocational education, applied research, and engagement with the ne...
Compliance Ranges Comparison
Technology Commercialization Office of the George Washington University
RMIT University
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Technology Commercialization Office of the George Washington University in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for RMIT University in 2026.
Incident History - Technology Commercialization Office of the George Washington University (X = Date, Y = Severity)
Technology Commercialization Office of the George Washington University cyber incidents detection timeline including parent company and subsidiaries.
Incident History - RMIT University (X = Date, Y = Severity)
RMIT University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Technology Commercialization Office of the George Washington University
RMIT University
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.