Comparison Overview
University of Louisville
University of Louisville
2301 S 3rd St, Louisville, ky, US, 40292-0001
Last Update: 01/04/2026
The University of Louisville is a state supported research university located in Kentucky's largest metropolitan area. It was a municipally supported public institution for many decades prior to joining the university system in 1970. The University has three campuses. T...
Northeastern University
360 Huntington Ave, Boston, MA, US, 02115-5005
Last Update: 01/04/2026
Founded in 1898, Northeastern is a global research university with a distinctive, experience-driven approach to education and discovery. The university is a leader in experiential learning, powered by the world’s most far-reaching cooperative education program. We inte...
Compliance Ranges Comparison
University of Louisville
Northeastern University
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for University of Louisville in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Northeastern University in 2026.
Incident History - University of Louisville (X = Date, Y = Severity)
University of Louisville cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Northeastern University (X = Date, Y = Severity)
Northeastern University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
University of Louisville
Northeastern 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.