Comparison Overview
Goodhope Asia Holdings Ltd

Goodhope Asia Holdings Ltd
Level 20, East Tower, World Trade Centre,, Echelon Square, Colombo 01, Colombo, Western Province, LK
Last Update: 02/11/2025
Goodhope Asia Holdings Ltd, incorporated in Singapore, is a holding company with investments in the food ingredient industry in Indonesia, Malaysia and India. Goodhope is a part of the group of companies that form Carson Cumberbatch PLC - a Sri Lankan conglomerate with...

Syngenta Group
Rosentalstrasse 67, Basel, 4002, CH
Last Update: 02/06/2026
To help feed 10 billion people while reducing emissions and improve biodiversity. This is our mission as the global agriculture technology leader. With over 56,000 employees in more than 90 countries and hundreds of thousands of agricultural partners worldwide, we are c...
Compliance Ranges Comparison

Goodhope Asia Holdings Ltd







Syngenta Group






Benchmark & Cyber Underwriting Signals
Incidents vs Farming Industry Avg (This Year)
No incidents recorded for Goodhope Asia Holdings Ltd in 2026.
Incidents vs Farming Industry Avg (This Year)
Syngenta Group has 4.76% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Goodhope Asia Holdings Ltd (X = Date, Y = Severity)
Goodhope Asia Holdings Ltd cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Syngenta Group (X = Date, Y = Severity)
Syngenta Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Goodhope Asia Holdings Ltd

Syngenta Group
FAQ
Latest Global CVEs
Deserialization of untrusted data in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.
The Bluetooth BAP Broadcast Assistant GATT client in subsys/bluetooth/audio/bap_broadcast_assistant.c reassembled remote Broadcast Receive State data into a single file-static net_buf_simple (att_buf, BT_ATT_MAX_ATTRIBUTE_LEN = 512 bytes) shared by all connection instances, while the BUSY flag, long-read handle, and reset/offset state were per-connection. When the device acts as a Broadcast Assistant connected to multiple Scan Delegator peripherals, notification and long-read callbacks from different connections interleave on the shared buffer: the append in notify_handler (net_buf_simple_add_mem at the not-busy branch) performs no tailroom check, so receive-state notifications from two or more delegators accumulate on the same 512-byte buffer and, with a sufficiently large configured ATT MTU (BT_L2CAP_TX_MTU up to 2000) and two-to-three concurrent connections, write past the buffer into adjacent .bss (net_buf_simple_add only asserts in debug builds). Even below the overflow threshold, one connection's net_buf_simple_reset zeroes the shared length while another connection's reassembly and GATT read offset are in flight, mixing one peer's data into another's parse. A malicious or compromised Scan Delegator (or two colluding peers) over BLE can trigger this, causing out-of-bounds writes (memory corruption / denial of service) and cross-connection data corruption. The fix moves the buffer into the per-connection instance struct so each connection reassembles into its own buffer. Affects Zephyr releases shipping the Broadcast Assistant with the shared buffer, including v4.4.0 and earlier.
ImageMagick before 7.1.2-26 contains a memory leak vulnerability in the VIFF encoder when memory allocation fails. Attackers can trigger allocation failures by processing specially crafted VIFF images to exhaust available memory and cause denial of service.
ImageMagick before 7.1.2-26 contains a use-after-free vulnerability in the FormatMagickCaption method when memory allocation fails. Attackers can trigger memory allocation failures to cause a dangling pointer to reference freed memory, potentially enabling denial of service or code execution.
ImageMagick before 7.1.2-26 contains a policy bypass vulnerability in the APNG encoder and external delegates due to missing validation checks. Attackers can write files to disallowed paths by bypassing configured policy restrictions through the APNG encoding process.