Comparison Overview
Hightower Communications, Inc.

Hightower Communications, Inc.
105 W Caswell St, Kinston, 28501, US
Last Update: 02/06/2026
Hightower Communications Inc. stands as a leading wireless communications contractor in the Southeast region. With a strong reputation as an established tower construction company and an esteemed member of NATE (National Association of Tower Erectors), we maintain a wor...

e& UAE
Sheikh Rashid Bin Saeed Al Maktoum Street, Abu Dhabi, AE, 3838
Last Update: 30/05/2026
(Formerly etisalat UAE) For more than four decades, we have connected people and now we’ve evolved to become the digital telco of the future. Our mission is to grow, transform and excel as the region’s technology leader while enhancing digital customer experience and o...
Compliance Ranges Comparison

Hightower Communications, Inc.







e& UAE






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
Hightower Communications, Inc. has 45.95% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for e& UAE in 2026.
Incident History - Hightower Communications, Inc. (X = Date, Y = Severity)
Hightower Communications, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - e& UAE (X = Date, Y = Severity)
e& UAE cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Hightower Communications, Inc.

e& UAE
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.