Comparison Overview
Crédit Agricole Group Infrastructure Platform
Crédit Agricole Group Infrastructure Platform
83, Boulevard des Chênes, Guyancourt, Île-de-France, 78280, FR
Last Update: 19/03/2026
Crédit Agricole Group Infrastructure Platform a pour vocation de devenir un pôle technologique de 1er plan, attractif pour les collaborateurs, les nouveaux talents et les partenaires IT. Nos ambitions : développer de nouvelles plateformes adaptées aux pratiques du dig...
Nagarro
Munich, DE
Last Update: 31/03/2026
Nagarro helps future-proof your business through a forward-thinking, fluidic, and CARING mindset. We excel at digital engineering and help our clients become human-centric, digital-first organizations, augmenting their ability to be responsive, efficient, intimate, crea...
Compliance Ranges Comparison
Crédit Agricole Group Infrastructure Platform
Nagarro
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Crédit Agricole Group Infrastructure Platform in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Nagarro in 2026.
Incident History - Crédit Agricole Group Infrastructure Platform (X = Date, Y = Severity)
Crédit Agricole Group Infrastructure Platform cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Nagarro (X = Date, Y = Severity)
Nagarro cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Crédit Agricole Group Infrastructure Platform
Nagarro
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.