Caesar AI Atlas
Recrutement / RH
2025-06-30Cas #2

La plateforme de recrutement par IA McHire de McDonald’s aurait exposé les données de 64 millions de candidats via un identifiant par défaut et une vulnérabilité d’API

Résumé de l'incident

Les chercheurs Ian Carroll et Sam Curry ont rapporté que l’outil de recrutement alimenté par l’IA de McDonald’s, McHire (utilisant le chatbot « Olivia » de Paradox.ai), aurait pu être consulté au moyen d’identifiants administrateur par défaut et d’une référence directe non sécurisée à un objet dans une API interne. Ces failles auraient permis de consulter les informations personnellement identifiables des candidats et les historiques de conversation. McDonald’s et Paradox auraient corrigé les problèmes dans la journée suivant la divulgation ; Paradox a déclaré que seuls cinq dossiers avaient été consultés.

Dossier de conformité

Gestion pratique des risques d'entreprise et réglementations

Impact commercial & risques PME

The default password vulnerability ('123456') and Insecure Direct Object Reference (IDOR) API vulnerability in the Paradox.ai platform exposed the highly sensitive personally identifiable information (PII), resumes, background check details, and chat histories of over 64 million job applicants. Researchers Ian Carroll and Sam Curry bypassed authentication on a franchisee login portal by entering the default credentials '123456' / '123456'. Once inside the live administrative dashboard, they discovered an unauthenticated API endpoint that fetched candidate records via a predictable ID parameter. By simply decrementing this ID, they could download candidates' complete resumes, shift preferences, personality tests, and OAuth session tokens. The primary business exposure for implementing firms is extreme liability under global data protection frameworks like GDPR (penalties up to 4% of global turnover) and California's CCPA, alongside class-action lawsuits and severe brand damage to employer reputation. Regulatory Impact Alignment: HR candidate evaluation, job-ad optimization, and screening algorithms are designated as High-Risk AI systems under EU AI Act Article 6 and Article 27. Compliance requires executing systematic Data Protection Impact Assessments (DPIAs), maintaining immutable server logs, and verifying that pre-employment tools adhere to EEOC Title VII guidelines on disparate selection rates to prevent automated racial, age, or gender discrimination.

Leçon de conformité clé

AI-driven interfaces and conversational chatbots are fundamentally tied to backend databases, APIs, and microservices. A beautiful AI frontend often masks insecure backend architectures. Organizations must not assume that a vendor's cutting-edge AI translates to robust cybersecurity. Rigorous pre-procurement vendor audits, regular penetration testing, and secure API routing are mandatory controls. Compliance Audit Standards: For detailed verification audits, this case maps directly under EU AI Act Article 6 (High-Risk Classification) & EEOC Title VII Alignment. Systems deploying similar AI features must maintain dynamic security logs and hold systematic compliance records.

Plan d'action étape par étape

  • 1Pre-Procurement Vendor Audits: Enforce strict pre-procurement security questionnaires, checking for SOC 2 Type II or ISO 27001 certifications before deploying any third-party AI HR-tech systems.
  • 2Decommission Legacy Portals: Disable all legacy administrative bypass portals, mandate Single Sign-On (SSO) integration, and require Multi-Factor Authentication (MFA) for all franchisee logins.
  • 3Automated API Scanning: Integrate continuous automated API scanning tools to detect and eliminate IDOR (Insecure Direct Object Reference) vulnerabilities on all candidate-facing endpoints.
  • 4Data Protection Agreements: Mandate that all AI vendors sign comprehensive Data Protection Agreements (DPAs) detailing liability, data breach notification timelines, and data destruction guidelines.
  • 5Disparate Impact Audit: Conduct annual statistical audits using the 80% selection rule to verify zero demographic bias in automated filters.
  • 6Cryptographic Consent Logs: Enforce strict local database encryption and cryptographically sign candidate consent logs for biometric checks.
  • 7Conformance Trail Retention: Retain secure server-side event logs capturing all automated candidate classification logs for 5 years.

Commentaire d'expert en conformité

Professional compliance incident analysis

This incident represents the classic 'AI shadow risk.' Companies rush to integrate trendy recruiting chatbots like Paradox Olivia to cut operational costs but ignore basic cybersecurity hygiene like changing default admin credentials. In the regulated AI world, a sophisticated algorithm is worthless if the backend is a sieve. Audit your vendors before the regulator audits you.

Nuances du glossaire IA & terminologie

AI Compliance FAQ

Critical answers regarding AI compliance, auditing, and organizational risks

QWhat is an IDOR vulnerability in an AI system?

An Insecure Direct Object Reference (IDOR) occurs when an API endpoint uses a predictable parameter (such as a sequential ID) to access database records without verifying the user's authorization to view that specific record.

QHow did researchers bypass McHire's Single Sign-On (SSO) protection?

Although the platform utilized SSO, it retained a legacy login link designed for 'Paradox Team Members' that bypassed SSO and accepted default credentials ('123456' / '123456') to grant full admin access.

QWhat are the GDPR liabilities for HR chatbot database leaks?

Under GDPR, companies face regulatory fines up to 4% of their global annual turnover or €20 million, alongside massive class-action lawsuit liabilities for failing to protect applicant personally identifiable information (PII).

Parties prenantes de l'incident

Déployeurs du système

McdonaldsParadox.Ai

Développeurs du système

McdonaldsParadox.Ai

Parties lésées

Candidats A Mcdonalds

Sources auditables (3)

Dossiers similaires recommandés