Comparison Overview
Alam Sekitar Malaysia Sdn Bhd
Alam Sekitar Malaysia Sdn Bhd
Lot 10, Jalan Astaka U8/84, Bukit Jelutong Business And Technology Centre, , Shah Alam, 40150 , MY
Last Update: 06/12/2025
Incorporated in May of 1993, Alam Sekitar Malaysia Sdn. Bhd. (ASMA) is a private company under the PICORP Group of Companies that provides total environmental solutions to clients ranging from governments (local authorities, states and federal governments) to industries...
Clean Harbors
42 Longwater Drive, Norwell, 02061-9149, US
Last Update: 30/03/2026
Clean Harbors is North America’s leading provider of environmental and industrial services. The Company serves a diverse customer base, including a majority of Fortune 500 companies. Its customer base spans a number of industries, including chemical, and manufacturing, ...
Compliance Ranges Comparison
Alam Sekitar Malaysia Sdn Bhd
Clean Harbors
Benchmark & Cyber Underwriting Signals
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Alam Sekitar Malaysia Sdn Bhd in 2026.
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Clean Harbors in 2026.
Incident History - Alam Sekitar Malaysia Sdn Bhd (X = Date, Y = Severity)
Alam Sekitar Malaysia Sdn Bhd cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Clean Harbors (X = Date, Y = Severity)
Clean Harbors cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Alam Sekitar Malaysia Sdn Bhd
Clean Harbors
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: *.*.