Comparison Overview
Hefei Institutes of Physical Science, Chinese Academy of Sciences, Hefei, Anhui 230029, P.R.China
Hefei Institutes of Physical Science, Chinese Academy of Sciences, Hefei, Anhui 230029, P.R.China
N/A
Last Update: 31/03/2026
Hefei Institutes of Physical Science, Chinese Academy of Sciences（CASHIPS）, Formerly the Hefei Branch of CAS founded in 1978, is composed of 5 institutes, the Institute of Plasma Physics (IPP), the Institute of Solid State Physics (ISSP)，Anhui Institute of Optics and Fi...
Penn State University
201 Old Main, University Park, pa, US, 16802-1589
Last Update: 02/04/2026
There’s a reason Penn State consistently ranks among the top one percent of the world’s universities. Across 24 campuses, our nearly 88,000 students and 17,000 faculty and staff know the real measure of success goes beyond the classroom—it’s the positive impact made on ...
Compliance Ranges Comparison
Hefei Institutes of Physical Science, Chinese Academy of Sciences, Hefei, Anhui 230029, P.R.China
Penn State University
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Hefei Institutes of Physical Science, Chinese Academy of Sciences, Hefei, Anhui 230029, P.R.China in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Penn State University in 2026.
Incident History - Hefei Institutes of Physical Science, Chinese Academy of Sciences, Hefei, Anhui 230029, P.R.China (X = Date, Y = Severity)
Hefei Institutes of Physical Science, Chinese Academy of Sciences, Hefei, Anhui 230029, P.R.China cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Penn State University (X = Date, Y = Severity)
Penn State University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hefei Institutes of Physical Science, Chinese Academy of Sciences, Hefei, Anhui 230029, P.R.China
Penn 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.