Comparison Overview
Infinity Reply DE

Infinity Reply DE
Luise-Ullrich-Straße 14, München, 80636, DE
Last Update: 20/12/2025
Infinity Reply ist ein Serviceunternehmen, das seine Kunden bezüglich Einsatz, Nutzung und Implementierung von 3D-Visualisierungslösungen, unter anderem auf Basis von Virtual und Augmented Reality (VR und AR), berät und bei der Umsetzung professionell begleitet. Mit uns...

TELUS Digital
510 West Georgia Street, Vancouver, V6B 0M3, CA
Last Update: 01/04/2026
TELUS Digital crafts unique and enduring experiences for customers and employees, and creates future-focused digital transformations that stand the test of time. We are the brand behind the brands. Our global team members are both passionate ambassadors of our clients’ ...
Compliance Ranges Comparison

Infinity Reply DE







TELUS Digital






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Infinity Reply DE in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
TELUS Digital has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - Infinity Reply DE (X = Date, Y = Severity)
Infinity Reply DE cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TELUS Digital (X = Date, Y = Severity)
TELUS Digital cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Infinity Reply DE

TELUS Digital
FAQ
Latest Global CVEs
A flaw has been found in code-projects Online Food Order System 1.0. The impacted element is an unknown function of the file delete_food_items1.php. Executing a manipulation of the argument checkbox can lead to sql injection. The attack can be executed remotely. The exploit has been published and may be used.
Pandora contains a denial-of-service vulnerability in its handling of DAA (Direct Access Archive) files. When extracting the internal ISO image from a DAA archive, compressed chunks were decompressed using zlib.decompress() without enforcing a limit on the resulting uncompressed data. An attacker able to submit a crafted DAA file containing highly compressed data could cause Pandora to decompress a relatively small input into a very large amount of data in memory. Because the decompressed chunks are accumulated to construct the internal ISO image, this could result in excessive memory consumption and potentially CPU exhaustion, causing the extraction worker to become unresponsive, terminate, or affect the availability of the Pandora service. The patch introduces bounded decompression using decompressobj().decompress() with max_extracted_filesize, verifies the cumulative size of decompressed chunks, and raises a dedicated ZipBomb exception when the configured limit is exceeded. Pandora then aborts extraction and reports the file as too large.
Pandora contains a path traversal vulnerability in its TAR archive extraction functionality. When processing a submitted TAR archive, the extractor passed archive member names directly to Python's tarfile.TarFile.extract() without applying an extraction filter. An attacker able to submit a specially crafted TAR archive containing malicious member paths, such as paths using ../ sequences or absolute paths, could cause extracted files to be written outside the intended extraction directory. This may allow the attacker to overwrite files accessible to the Pandora worker process and could potentially result in application compromise, arbitrary code execution, or denial of service depending on the files targeted and the privileges of the Pandora process. The vulnerability is corrected by using Python's filter='data' extraction filter, which rejects or sanitizes dangerous TAR members, including paths that escape the destination directory and unsafe link targets. The weakness corresponds to MITRE's general path traversal category, which includes archive extraction cases where attacker-controlled filenames cause files to be written outside the intended directory.
Shescape before 2.1.15 (and 3.0.0 before 3.0.2) fails to properly escape tilde (~) characters in assignment contexts on Unix systems where the shell is explicitly configured to "sh" or true and /bin/sh points to BusyBox. Using the escape and escapeAll APIs with untrusted input in an assignment prefixed to a command, an attacker can inject a tilde payload to disclose the user's home directory location and, depending on usage, alter the location on which a command operates.
- https://github.com/ericcornelissen/shescape/commit/7cba30594c16a21524706efe2f6c6c9d8923f411
- https://github.com/ericcornelissen/shescape/commit/d86bf2ae22961c73458bddf70dd06adf9dadb36c
- https://github.com/ericcornelissen/shescape/security/advisories/GHSA-j44h-fqhh-fh28
- https://www.vulncheck.com/advisories/shescape-before-home-directory-disclosure-via-busybox
SiYuan versions before v3.7.4 contain an authentication bypass vulnerability in the WebSocket endpoint caused by differential parsing of query parameters between authentication exemption and session quarantine checks. Unauthenticated attackers can craft a malicious WebSocket URI with duplicated query parameters to bypass access auth code validation and receive the live kernel event stream including document identifiers, titles, and operation logs.