Comparison Overview
U.S. Department of Homeland Security, Office of Intelligence and Analysis, Private Sector Engagement
U.S. Department of Homeland Security, Office of Intelligence and Analysis, Private Sector Engagement
3801 Nebraska Ave NW, Washington, 20016, US
Last Update: 07/03/2026
Private Sector Engagement’s mission: Ensure that Private Sector critical infrastructure owners and operators and Private Sector decision-makers are equipped with the intelligence and information necessary to fulfill their mission requirements Follow this page for progr...
State of Illinois
US
Last Update: 01/04/2026
The government of Illinois, under the Constitution of Illinois, has three branches of government: executive, legislative and judicial. The executive branch is split into several statewide elected offices, with the Governor as chief executive, and has numerous department...
Compliance Ranges Comparison
U.S. Department of Homeland Security, Office of Intelligence and Analysis, Private Sector Engagement
State of Illinois
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for U.S. Department of Homeland Security, Office of Intelligence and Analysis, Private Sector Engagement in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for State of Illinois in 2026.
Incident History - U.S. Department of Homeland Security, Office of Intelligence and Analysis, Private Sector Engagement (X = Date, Y = Severity)
U.S. Department of Homeland Security, Office of Intelligence and Analysis, Private Sector Engagement cyber incidents detection timeline including parent company and subsidiaries.
Incident History - State of Illinois (X = Date, Y = Severity)
State of Illinois cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
U.S. Department of Homeland Security, Office of Intelligence and Analysis, Private Sector Engagement
State of Illinois
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.