Comparison Overview
GSMA Latin America

GSMA Latin America
Av. Del Libertador 6810 15th Floor, Buenos Aires, C1429BMO, AR
Last Update: 17/02/2026
La GSMA es una organización global que une al ecosistema móvil para descubrir, desarrollar y ofrecer innovación esencial para entornos comerciales positivos y cambios sociales. Nuestra visión consiste en liberar todo el poder de la conectividad para que las personas, la...

Bell
1 carrefour Alexandre-Graham-Bell, Montreal, Quebec, CA, H3E 3B3
Last Update: 01/04/2026
We advance how people connect with each other and the world #ConnectionIsEverything. Bell is Canada's largest communications company providing advanced Bell broadband wireless, Internet, TV, media and business communications services. Founded in Montréal in 1880, Bell...
Compliance Ranges Comparison

GSMA Latin America







Bell






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for GSMA Latin America in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
Bell has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - GSMA Latin America (X = Date, Y = Severity)
GSMA Latin America cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bell (X = Date, Y = Severity)
Bell cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

GSMA Latin America

Bell
FAQ
Latest Global CVEs
A vulnerability has been found in SourceCodester Simple Online Food Ordering System 1.0. This affects an unknown function of the file /admin/ajax.php?action=login2. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
A flaw was found in the ipa_getkeytab module of the community.general Ansible collection. The module's bind_pw parameter, used to supply the LDAP simple-bind password when retrieving a Kerberos keytab, is not declared with no_log, unlike the sibling password parameter in the same module. As a consequence, the supplied IPA/LDAP bind password is recorded in cleartext in the managed host's system journal/syslog (the module's "Invoked with" record), is included in the module's return values and verbose (-v) output, and is displayed in Automation Controller / AWX job output. The password is additionally passed on the command line to the ipa-getkeytab helper (as --bindpw <value>), exposing it in the process list to local users while the command runs. An attacker able to read these logs, job output, or the process table can obtain the directory bind credential, potentially compromising the accounts and objects that credential can access.
The device metadata import interface /device/instance/{productId}/property-metadata/import of jetlinks community 2.11 is vulnerable to Server-side request forgery (SSRF).
disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
Funiture 1.0.0 is vulnerable to SQL Injection in the backend tool interfaces /sys/tool/select.json and /sys/tool/update.json.