Comparison Overview
Allianz Trade in Deutschland
Allianz Trade in Deutschland
Gasstrasse 29, Hamburg, 22761, DE
Last Update: 13/03/2026
Allianz Trade is the trademark used to designate a range of services provided by Euler Hermes. We are the global leader in trade credit insurance and a recognized specialist in the areas of surety, collections, structured trade credit and political risk. For over a cen...
Marsh Risk
1166 Avenue of the Americas, New York, New York, US, 10036
Last Update: 01/04/2026
We help our clients and colleagues grow — and our communities thrive — by protecting and promoting possibility. We seek better ways to manage risk and define more effective paths to the right outcome. We go beyond risk to rewards for our clients, our company, our collea...
Compliance Ranges Comparison
Allianz Trade in Deutschland
Marsh Risk
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Allianz Trade in Deutschland in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Marsh Risk in 2026.
Incident History - Allianz Trade in Deutschland (X = Date, Y = Severity)
Allianz Trade in Deutschland cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Marsh Risk (X = Date, Y = Severity)
Marsh Risk cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Allianz Trade in Deutschland
Marsh Risk
FAQ
Latest Global CVEs
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). A low-privileged authenticated user can send a specially crafted request to a Kibana machine learning feature, causing the server to exhaust available memory and become unavailable to all users.
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated attacker with low-privilege access can trigger a denial of service condition in Kibana by sending a specially crafted, oversized request payload. Processing this user-supplied input requires resource-intensive memory allocation that can exhaust the available heap memory in the Kibana process, causing it to crash and become unavailable to all users.
Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to information disclosure via user-supplied identifiers that reference scheduled query result data from Kibana Spaces the requester is not authorized to access.
Incorrect Authorization (CWE-863) in Kibana can lead to integrity compromise of Machine Learning audit and notification records via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). A vulnerability exists in Kibana's Machine Learning functionality where a Machine Learning management endpoint performs an insufficient authorization check. The endpoint validates only a coarse privilege level but does not verify that the requesting user has access to the specific Machine Learning job or notification resources provided in the request. As a result, a low-privileged user with Machine Learning access in any Kibana space can manipulate Machine Learning audit and notification records for arbitrary jobs—including jobs in other spaces or belonging to other users—by leveraging Kibana's internally elevated credentials to write to restricted Machine Learning system indices that the user cannot access directly.
Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to denial of service via a specially crafted search request submitted by a low-privileged authenticated user. A user with read-level index access can submit a request that triggers unbounded recursive processing within the Elasticsearch query evaluation component, causing a fatal error that terminates the affected node. In single-node deployments, this results in complete service outage; in multi-node clusters, it causes repeated node restarts and sustained availability degradation.