Comparison Overview
Chiyoda Singapore (Pte) Ltd
Chiyoda Singapore (Pte) Ltd
14 International Business Park, Jurong East, Singapore, Singapore, 609922, SG
Last Update: 04/12/2025
Chiyoda Corporation (formerly known as Chiyoda Chemical Engineering & Construction Co. Ltd., Japan) first ventured into Singapore in the year 1964 to participate in the design and construction of Mobil's first petroleum refinery. With its successful completion of the g...
ConocoPhillips
925 N Eldridge Pkwy, Houston, 77079, US
Last Update: 01/04/2026
We are a global oil and gas company tasked with an important job—to safely find and deliver energy for the world. We’re experts in what we do—from the well site to the office. Across our operations and activities in 13 countries, we never forget our responsibility to ...
Compliance Ranges Comparison
Chiyoda Singapore (Pte) Ltd
ConocoPhillips
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Chiyoda Singapore (Pte) Ltd in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for ConocoPhillips in 2026.
Incident History - Chiyoda Singapore (Pte) Ltd (X = Date, Y = Severity)
Chiyoda Singapore (Pte) Ltd cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ConocoPhillips (X = Date, Y = Severity)
ConocoPhillips cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Chiyoda Singapore (Pte) Ltd
ConocoPhillips
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: *.*.