Comparison Overview
GreenYellow South Africa
GreenYellow South Africa
205 Rivonia Road, Sandton, 2196, ZA
Last Update: 31/01/2026
In light of South Africa's commitment to energy transition and the urgent need for concrete action on climate change, GreenYellow wishes to support the country's private and public stakeholders to make the green growth a reality shared by all. As a Partner in the energy...
Siemens Gamesa
Parque Tecnológico de Bizkaia, edificio 222, Zamudio, 48170, ES
Last Update: 01/04/2026
Siemens Gamesa is a global technology leader in the renewable energy industry - specifically in the development, manufacturing, installation and maintenance of wind turbines. Being a pioneer in renewables since the 1980s, we put our scale and entrepreneurial culture to ...
Compliance Ranges Comparison
GreenYellow South Africa
Siemens Gamesa
Benchmark & Cyber Underwriting Signals
Incidents vs Renewable Energy Semiconductor Manufacturing Industry Avg (This Year)
No incidents recorded for GreenYellow South Africa in 2026.
Incidents vs Renewable Energy Semiconductor Manufacturing Industry Avg (This Year)
No incidents recorded for Siemens Gamesa in 2026.
Incident History - GreenYellow South Africa (X = Date, Y = Severity)
GreenYellow South Africa cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Siemens Gamesa (X = Date, Y = Severity)
Siemens Gamesa cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
GreenYellow South Africa
Siemens Gamesa
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.