Comparison Overview
Keystone Closing Services
Keystone Closing Services
9600 Perry Hwy 100 Pittsburgh, Pennsylvania 15237, US
Last Update: 27/10/2025
Keystone Closing Services is national in scope but locally staffed with the ability to provide title insurance in 43 states and closing services in 50 states. The company is built on a tradition of excellence and guided by a spirit of integrity throughout all aspects o...
Savills
33 Margaret Street, London, GB, W1G 0JD
Last Update: 01/04/2026
Savills is a global real estate advisor helping people thrive through places and spaces. With over 42,000 professionals in more than 700 offices across the Americas, Europe, Asia Pacific, Africa and the Middle East, we combine local knowledge with global insight to del...
Compliance Ranges Comparison
Keystone Closing Services
Savills
Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Keystone Closing Services in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Savills in 2026.
Incident History - Keystone Closing Services (X = Date, Y = Severity)
Keystone Closing Services cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Savills (X = Date, Y = Severity)
Savills cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Keystone Closing Services
Savills
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.