Comparison Overview
Perfect World Games

Perfect World Games
浦东新区世博大道, 宝武大厦2号楼9层, 上海, 上海, CN, 200120
Last Update: 09/03/2026
Since 2015, Perfect World has successfully hosted DOTA2 Asia Championships for three times, which were covered by mainstream media like the CCTV and successfully held CS:GO Asia Championships, which attracted significant public attention. The company has once again prom...

Dassault Systèmes
10, rue Marcel Dassault, Vélizy-Villacoublay, 78140, FR
Last Update: 19/06/2026
Dassault Systèmes is a catalyst for human progress. Since 1981, the company has pioneered virtual worlds to improve real life for consumers, patients and citizens. With Dassault Systèmes’ 3DEXPERIENCE platform, 370,000 customers of all sizes, in all industries, can co...
Compliance Ranges Comparison

Perfect World Games







Dassault Systèmes






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Perfect World Games in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Dassault Systèmes in 2026.
Incident History - Perfect World Games (X = Date, Y = Severity)
Perfect World Games cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dassault Systèmes (X = Date, Y = Severity)
Dassault Systèmes cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Perfect World Games

Dassault Systèmes
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.