Comparison Overview
Hyatt Regency Indianapolis
Hyatt Regency Indianapolis
One South Capitol Avenue, Indianapolis, Indiana, 46204, US
Last Update: 31/10/2025
Beautifully designed and refined, Hyatt Regency is a contemporary downtown Indianapolis hotel conveniently connected to the Convention Center and just steps from Lucas Oil Stadium. The modern amenities at our hotel blend effortlessly with classic design elements, creati...
Four Seasons Hotels and Resorts
1165 Leslie Street, Toronto, M3C 2K8, CA
Last Update: 05/04/2026
Four Seasons Hotels and Resorts opened its first hotel in 1961, and since that time has been dedicated to perfecting the travel experience through continual innovation and the highest standards of hospitality. Currently operating more than 130 hotels and resorts, and mo...
Compliance Ranges Comparison
Hyatt Regency Indianapolis
Four Seasons Hotels and Resorts
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Hyatt Regency Indianapolis in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Four Seasons Hotels and Resorts in 2026.
Incident History - Hyatt Regency Indianapolis (X = Date, Y = Severity)
Hyatt Regency Indianapolis cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Four Seasons Hotels and Resorts (X = Date, Y = Severity)
Four Seasons Hotels and Resorts cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hyatt Regency Indianapolis
Four Seasons Hotels and Resorts
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.