Comparison Overview
Reliance Communications
Reliance Communications
A Block, 2nd Floor, Reliance Communications Limited, DAKC, Kopar Khairane, Navi Mumbai, 400710, IN
Last Update: 01/04/2026
Reliance Communications Limited, founded by the late Shri Dhirubhai H Ambani (1932-2002), has Corporate clientele that includes 40,000 Indian and multinational corporations, including small and medium enterprises. Reliance Communications has established a pan-India, Ne...
Proximus Group
Boulevard du Roi Albert II 27, Brussels, 1030, BE
Last Update: 01/04/2026
Proximus Group is a provider of future-proof connectivity, IT and digital services, headquartered in Brussels. The Group is actively engaged in building a connected world that people trust, so society blooms. The Domestic segment is focused on providing state-of-the ar...
Compliance Ranges Comparison
Reliance Communications
Proximus Group
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Reliance Communications in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Proximus Group in 2026.
Incident History - Reliance Communications (X = Date, Y = Severity)
Reliance Communications cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Proximus Group (X = Date, Y = Severity)
Proximus Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Reliance Communications
Proximus Group
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.