Comparison Overview
唐拉雅秀国际酒店 Tangla Hotels & Resorts

唐拉雅秀国际酒店 Tangla Hotels & Resorts
B-2 East 3rd Ring North Road, Beijing, Beijing, 100027, CN
Last Update: 20/12/2025
唐拉雅秀为海航酒店集团旗下的五星级酒店品牌,是我们在繁华世界中为客人用心打造的一片清净天地,让他们无论身在何方,都能全身心地享受宁静与自在。 唐拉雅秀系列品牌致力于将富有东方神韵和文化风情的系列酒店品牌带给世人,带到世界的每一个角落,将源于自然地美好祝福和现在酒店艺术完美结合,以东方的待客之道,让普天世人享受到大隐于市的美好酒店体验。 Tangla Hotels and Resorts shine for their admirable oriental artistry in hospitality service, height...

Whitbread
Whitbread Court, Houghton Regis, Dunstable, LU5 5XE, GB
Last Update: 12/07/2026
Whitbread PLC is the owner of the UK’s favourite hotel chain, Premier Inn, as well as restaurant brands, Beefeater, Brewers Fayre, Table Table, Bar + Block and Cookhouse and Pub. Whitbread employs more than 35,000 people in more than 1,200 Premier Inn hotels and restau...
Compliance Ranges Comparison

唐拉雅秀国际酒店 Tangla Hotels & Resorts







Whitbread






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for 唐拉雅秀国际酒店 Tangla Hotels & Resorts in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Whitbread in 2026.
Incident History - 唐拉雅秀国际酒店 Tangla Hotels & Resorts (X = Date, Y = Severity)
唐拉雅秀国际酒店 Tangla Hotels & Resorts cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Whitbread (X = Date, Y = Severity)
Whitbread cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

唐拉雅秀国际酒店 Tangla Hotels & Resorts

Whitbread
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.