Comparison Overview
School of Information - The University of Texas at Austin
School of Information - The University of Texas at Austin
1616 Guadalupe St, Suite #5.202, Austin, Texas, 78701-1213, US
Last Update: 29/11/2025
The School of Information (iSchool) at The University of Texas at Austin is a premier research and education program for the 21st century field of information. We are changing the future by engaging the present and preserving the past. Research and teaching at the iScho...
The University of Texas at Austin
1 University Station, Austin, TX, US, 78712
Last Update: 02/04/2026
The University of Texas at Austin is one of the largest public universities in the United States. Founded in 1883, the University has grown from a single building, eight teachers, two departments and 221 students to a 350-acre main campus with 21,000 faculty and staff, ...
Compliance Ranges Comparison
School of Information - The University of Texas at Austin
The University of Texas at Austin
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for School of Information - The University of Texas at Austin in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for The University of Texas at Austin in 2026.
Incident History - School of Information - The University of Texas at Austin (X = Date, Y = Severity)
School of Information - The University of Texas at Austin cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The University of Texas at Austin (X = Date, Y = Severity)
The University of Texas at Austin cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
School of Information - The University of Texas at Austin
The University of Texas at Austin
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.