Comparison Overview
Thomson Reuters Argentina

Thomson Reuters Argentina
Tucumán 1471, Ciudad Autónoma de Buenos Aires, 1050, AR
Last Update: 06/03/2026
Thomson Reuters provides professionals with the intelligence, technology and human expertise they need to find trusted answers. We enable leading decision makers to make the decisions that matter most across the financial and risk, legal, tax and accounting, intellec...

GLG
60 East 42nd Street, 3rd Floor, New York, NY, US, 10165
Last Update: 02/04/2026
GLG is the world’s largest insight network. We connect decision makers to the right experts so they can act with the confidence that comes from true clarity and have what it takes to get ahead. Our network of experts is the world’s largest source of first-hand expertise...
Compliance Ranges Comparison

Thomson Reuters Argentina







GLG






Benchmark & Cyber Underwriting Signals
Incidents vs Information Services Industry Avg (This Year)
No incidents recorded for Thomson Reuters Argentina in 2026.
Incidents vs Information Services Industry Avg (This Year)
No incidents recorded for GLG in 2026.
Incident History - Thomson Reuters Argentina (X = Date, Y = Severity)
Thomson Reuters Argentina cyber incidents detection timeline including parent company and subsidiaries.
Incident History - GLG (X = Date, Y = Severity)
GLG cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Thomson Reuters Argentina

GLG
FAQ
Latest Global CVEs
The CONS_HISTORY ioctl handler did not adequately validate the requested history size. A large value caused an integer overflow in the buffer size calculation, resulting in a heap allocation smaller than expected. Subsequent initialization of the buffer wrote beyond the end of the allocation. An unprivileged local user with access to a vt(4) device can trigger an out-of-bounds write in the kernel, potentially escalating privileges.
The ELF image activator cleared per-process ASLR preference flags for setuid binaries after the code that computes the PIE base address, rather than before. As a result, a user-requested ASLR disable was still in effect at the point where the base address was chosen. An unprivileged local user can disable ASLR for a setuid PIE binary by calling procctl(2) before execve(2). This makes exploitation of any separate memory corruption vulnerability in that binary significantly easier.
Second, the audio buffer backing a mapping could be freed when the device was closed even though the mapping remained valid. The freed memory could then be reused elsewhere while still accessible through the stale mapping. The /dev/dsp device nodes are world-accessible by default. On a system with an audio device, either issue allows an unprivileged local user to read and write kernel memory, which can be used to escalate privileges, potentially gaining full control of the affected system. At a minimum, an attacker can crash the kernel, resulting in a Denial of Service (DoS).
The Linuxulator determined whether a binary was set-user-ID or set-group-ID by checking the P_SUGID process flag. During execve(2), this flag is not yet set at the point where the auxiliary vector is constructed, so AT_SECURE was incorrectly set to zero for set-user-ID and set-group-ID executables. An unprivileged local user can inject a shared library via LD_PRELOAD into a set-user-ID or set-group-ID Linux binary, gaining the privileges of that binary.
The kernel handler for IPV6_MSFILTER dropped a serializing lock in order to copy the source-filter list from userspace, then reacquired the lock. During this window another thread could free the multicast filter structure, leaving the handler with a stale pointer to freed memory. An unprivileged local user can exploit this use-after-free to escalate privileges.