Comparison Overview
Tangla Hotel Beijing 北京唐拉雅秀酒店

Tangla Hotel Beijing 北京唐拉雅秀酒店
北京市复兴门外大街19号, 北京市, 北京市/西城区, 100045, CN
Last Update: 21/02/2026
秉赋东方之礼 盛放西贵长安 DISCOVERY TANGLA Hotel Beijing “唐拉雅秀”一词源自唐古拉山脉的一个美丽传说,诠释着生命与自然的和谐.“唐古拉山接云天,三江源水养丰年”。耸立在海拔五千米高原上的唐古拉山雄壮圣洁,美丽富饶。冰雪融化并汇集成生生不息的三江源水,孕育了华夏灿烂文明和她的亿万儿女。成百上千年来,唐拉雅秀统领着绵延数百公里的唐古拉山脉。他巍巍昆仑守护着在这里居住的善良的人们,用潺潺流水灌溉着这片富饶辽阔的土地。 北京唐拉雅秀酒店位居北京西长安街,地处首都政务金融核心区域,距金融街一步之遥,距天安门...

Club Med
Paris, FR
Last Update: 04/04/2026
Since it was founded in 1950 and it created the all-inclusive vacation concept, Club Med has been the world leader on its market, and has developed a resolutely upscale, friendly and multicultural spirit. Club Med boasts 70 resorts located in the most beautiful sites in...
Compliance Ranges Comparison

Tangla Hotel Beijing 北京唐拉雅秀酒店







Club Med






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

Tangla Hotel Beijing 北京唐拉雅秀酒店

Club Med
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.