Comparison Overview
DraftSight

DraftSight
75 Wyman St, Waltham, 02451, US
Last Update: 21/02/2026
DraftSight is brought to you by Dassault Systèmes, the 3DEXPERIENCE company, has been trusted by millions of users worldwide. DraftSight provides a familiar, intuitive 2D drafting experience with options for advanced productivity tools, 3D design capabilities, paramet...

SAP
Dietmar-Hopp-Allee 16, Walldorf, 69190, DE
Last Update: 12/08/2026
SAP is a global leader in enterprise applications and business AI. We help organizations run mission-critical operations across finance, procurement, supply chain, human resources, and customer experience -and move from systems that record work to systems that can help ...
Compliance Ranges Comparison

DraftSight







SAP






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for DraftSight in 2026.
Incidents vs Software Development Industry Avg (This Year)
SAP has 288.35% more incidents than the average of all companies with at least one recorded incident.
Incident History - DraftSight (X = Date, Y = Severity)
DraftSight cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SAP (X = Date, Y = Severity)
SAP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

DraftSight

SAP
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.