Comparison Overview
Thomson Reuters Brasil - ONESOURCE™ Global Trade

Thomson Reuters Brasil - ONESOURCE™ Global Trade
Rua Orlando Fagnani, 422, Nova Campinas – Campinas SP, None, Campinas, SP, BR, 13092-054
Last Update: 06/12/2025
Unidade de negócio da Thomson Reuters exclusiva para a solução de gerenciamento e automação do segmento de Comércio Exterior. Desenvolvida para atender companhias de qualquer tamanho ou setor da economia, traz um extenso portfólio de módulos que contribuem para um alt...

Infinite Computer Solutions
Tower Oaks Blvd, #700, Rockville, Maryland, US, 20852
Last Update: 17/06/2026
Infinite is a global leader in technology modernization, next-gen IT services and solutions, and digital engineering, with over two decades of experience helping clients turn digital transformation into business value. Leveraging an AI-first approach, we combine leading...
Compliance Ranges Comparison

Thomson Reuters Brasil - ONESOURCE™ Global Trade







Infinite Computer Solutions






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Thomson Reuters Brasil - ONESOURCE™ Global Trade in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Infinite Computer Solutions has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Thomson Reuters Brasil - ONESOURCE™ Global Trade (X = Date, Y = Severity)
Thomson Reuters Brasil - ONESOURCE™ Global Trade cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Infinite Computer Solutions (X = Date, Y = Severity)
Infinite Computer Solutions cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Thomson Reuters Brasil - ONESOURCE™ Global Trade

Infinite Computer Solutions
FAQ
Latest Global CVEs
A vulnerability was identified in Databend up to 1.2.881 on HTTP. This affects the function ClientSessionManager::state_key of the file src/query/service/src/servers/http/v1/session/client_session_manager.rs of the component Tenant Handler. The manipulation leads to authorization bypass. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The pull request to fix this issue awaits acceptance.
A vulnerability was determined in VoltAgent up to 2.1.17. Affected by this issue is the function handleGetMemoryConversation of the file packages/server-core/src/handlers/memory.handlers.ts of the component Memory REST API. Executing a manipulation of the argument conversationId can lead to improper authorization. The attack may be performed from remote. This attack is characterized by high complexity. The exploitation is known to be difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
A vulnerability was found in SimStudioAI sim up to 0.6.92. Affected by this vulnerability is an unknown functionality in the library apps/sim/lib/core/security/deployment.ts of the component Password Protection Handler. Performing a manipulation results in use of weak hash. The attack is possible to be carried out remotely. The attack's complexity is rated as high. The exploitation appears to be difficult. The exploit has been made public and could be used. The pull request to fix this issue awaits acceptance.
A vulnerability has been found in RAGapp up to 0.1.5. Affected is the function FileHandler.upload_file/FileHandler.remove_file of the file src/ragapp/backend/controllers/files.py of the component Knowledge File Handler. Such manipulation leads to path traversal. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.
A flaw has been found in khoj-ai khoj up to 2.0.0-beta.28. This impacts an unknown function of the file src/khoj/routers/api_chat.py of the component Conversation Sharing Handler. This manipulation of the argument conversation.agent causes incorrect authorization. Remote exploitation of the attack is possible. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.