Comparison Overview
Wirtschaftswissenschaftliche Fakultät – Georg-August-Universität Göttingen
Wirtschaftswissenschaftliche Fakultät – Georg-August-Universität Göttingen
Platz der Göttinger Sieben 3, Göttingen, 37073, DE
Last Update: 01/02/2026
Since the Georg-August-Universität Göttingen was founded in 1737, teaching economics to students has been a core element of the university's research and teaching activities. Today, the Faculty of Business and Economics is one of the largest in Germany, with around 3,40...
The California State University
401 Golden Shore, Long Beach, CA, US, 90802
Last Update: 07/05/2026
The California State University is the largest system of four-year higher education in the country, with 22 campuses, 56,000 faculty and staff and more than 450,000 students. Created in 1960, the mission of the CSU is to provide high-quality, affordable education to m...
Compliance Ranges Comparison
Wirtschaftswissenschaftliche Fakultät – Georg-August-Universität Göttingen
The California State University
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Wirtschaftswissenschaftliche Fakultät – Georg-August-Universität Göttingen in 2026.
Incidents vs Higher Education Industry Avg (This Year)
The California State University has 3.85% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Wirtschaftswissenschaftliche Fakultät – Georg-August-Universität Göttingen (X = Date, Y = Severity)
Wirtschaftswissenschaftliche Fakultät – Georg-August-Universität Göttingen cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The California State University (X = Date, Y = Severity)
The California State University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Wirtschaftswissenschaftliche Fakultät – Georg-August-Universität Göttingen
The California State University
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.