Comparison Overview
Ritchie Bros. Financial Services

Ritchie Bros. Financial Services
9500 Glenlyon Pkwy, Burnaby, V5J 0C6, CA
Last Update: 01/04/2026
Ritchie Bros. Financial Services is a dynamic, fast-paced and passionate equipment financing business headquartered in Burnaby, British Columbia. We created PurchaseFlex™ Financing to get you fast approvals and the freedom and flexibility to buy what you need, when you...

LPL Financial
4707 Executive Drive, San Diego, CA, US, 92121-1968
Last Update: 02/06/2026
LPL Financial Holdings Inc. (Nasdaq: LPLA) is among the fastest growing wealth management firms in the U.S. As a leader in the financial advisor-mediated marketplace, LPL supports over 29,000 financial advisors and the wealth management practices of approximately 1,100 ...
Compliance Ranges Comparison

Ritchie Bros. Financial Services







LPL Financial






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

Ritchie Bros. Financial Services

LPL Financial
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.