Comparison Overview
VIPRE Security Group Nordics
VIPRE Security Group Nordics
Spotorno Alle 12, Tåstrup, Capital Region, 2630, DK
Last Update: 03/12/2025
VIPRE Security Group har mere end 20 års brancheerfaring og er en førende leverandør af helhedsløsninger inden for it-sikkerhed. VIPRE leverer uovertruffen beskyttelse mod selv de mest aggressive trusler på nettet. Vores stærke software-portefølje inkluderer omfattende ...
Ricoh USA, Inc.
300 Eagleview Blvd, Exton, 19341, US
Last Update: 29/03/2026
At Ricoh, we bring people, processes, and technology together to make information work for you. We unlock the power of information so organizations can unlock the full potential of their people. We're a leader in information management and digital services, creating com...
Compliance Ranges Comparison
VIPRE Security Group Nordics
Ricoh USA, Inc.
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for VIPRE Security Group Nordics in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Ricoh USA, Inc. in 2026.
Incident History - VIPRE Security Group Nordics (X = Date, Y = Severity)
VIPRE Security Group Nordics cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ricoh USA, Inc. (X = Date, Y = Severity)
Ricoh USA, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
VIPRE Security Group Nordics
Ricoh USA, Inc.
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.