Comparison Overview
DXC providing claims management services

DXC providing claims management services
380 Docklands Drive, Level 2, Melbourne, Victoria, AU, 3008
Last Update: 04/04/2026
DXC provides policy and claims management services to organisations across Australia. Previously known as Xchanging, we continue to be a specialist provider supporting organisations and injured citizens throughout the entire claims process. DXC has demonstrated through ...

Aflac
1932 Wynnton Rd, Columbus, 31999, US
Last Update: 01/04/2026
Over 50 Million people worldwide have chosen Aflac because of our commitment to providing customers with the confidence that comes from knowing they have assistance in being prepared for whatever life may bring. With Aflac, whether you're a large business or a small o...
Compliance Ranges Comparison

DXC providing claims management services







Aflac






Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for DXC providing claims management services in 2026.
Incidents vs Insurance Industry Avg (This Year)
Aflac has 7.41% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - DXC providing claims management services (X = Date, Y = Severity)
DXC providing claims management services cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aflac (X = Date, Y = Severity)
Aflac cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

DXC providing claims management services

Aflac
FAQ
Latest Global CVEs
An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command
The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.
An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS. Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.
The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.
An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.