Comparison Overview
Deutsche Telekom IoT
Deutsche Telekom IoT
Landgrabenweg 149, Bonn, 53227, DE
Last Update: 21/01/2026
Deutsche Telekom IoT (DT IoT) is the global IoT Connector. Leveraging our leading transatlantic network, we provide platform-based, flexible connectivity solutions that simplify complex IoT deployments for businesses worldwide. With a seamless global footprint, our serv...
Gainwell Technologies
United States, US
Last Update: 22/05/2026
For 50 years, our nation’s federal Medicaid program has worked to improve the health, safety and well-being of America’s most vulnerable populations: low-income families, women and children, seniors, and those with disabilities. With positive health and cost outcomes th...
Compliance Ranges Comparison
Deutsche Telekom IoT
Gainwell Technologies
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Deutsche Telekom IoT in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Gainwell Technologies has 3.85% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Deutsche Telekom IoT (X = Date, Y = Severity)
Deutsche Telekom IoT cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Gainwell Technologies (X = Date, Y = Severity)
Gainwell Technologies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Deutsche Telekom IoT
Gainwell Technologies
FAQ
Latest Global CVEs
goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.5, the httpserver/handler.go sendFile handler opened files using a cleaned path but derived the authorization filename from raw req.URL.Path, so a trailing slash could bypass .goshs ACL-file protection and block-list checks. This issue is fixed in version 2.1.5.
goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.5, the httpserver/updown.go multipart upload handler split part.FileName() on / but did not reject .., allowing an unauthenticated upload with filename .. to create a file outside the served tree. This issue is fixed in version 2.1.5.
goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.4, the httpserver/server.go wdGuard handled WebDAV MOVE as a write-only method and did not enforce --no-delete, allowing WebDAV clients to delete or overwrite files via MOVE with Overwrite: T. This issue is fixed in version 2.1.4.
goshs is a feature-rich single-binary file server for red teamers and developers. From 2.1.3 until 2.1.4, the sftpserver/sftpserver.go password handler used Username != "" && Password != "", so running goshs with -b 'admin:' -sftp and no -fkf left both SFTP authentication handlers unset and allowed unauthenticated file access. This issue is fixed in version 2.1.4.
Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, HttpPostRequestEncoder constructs multipart HTTP request bodies by directly concatenating user-supplied filenames and field names into Content-Disposition MIME headers without validating or sanitizing CRLF characters (\r\n). Since MIME headers are delimited by CRLF, an attacker who controls the filename can inject arbitrary MIME headers into the multipart body part. The root cause is that neither the encoder nor the FileUpload implementations' setFilename() methods, which only check for null, neutralize CRLF characters before the filename is embedded into the header. This issue has been fixed in versions 4.1.136.Final and 4.2.16.Final.