AVID-2023-V023

Vulnerability from avid – Published: 2023-03-30 – Updated: 2023-03-30 AIID Incident
Summary
Kronos’s scheduling algorithm and its use by Starbucks managers allegedly negatively impacted financial and scheduling stability for Starbucks employees, which disadvantaged wage workers.
Risk domain
Performance
SEP view
P0401: Psychological Safety, P0403: Socioeconomic safety
Lifecycle
L06: Deployment
Organisations
Strbucks (deployer), Kronos (developer)
References
URL Label
https://incidentdatabase.ai/cite/10 Incident 10: Kronos Scheduling Algorithm Allegedly Caused Financial Issues for Starbucks Employees
To clipboard 

{
  "affects": {
    "artifacts": [
      {
        "name": "",
        "type": "System"
      }
    ],
    "deployer": [
      "Strbucks"
    ],
    "developer": [
      "Kronos"
    ]
  },
  "credit": [
    {
      "lang": "eng",
      "value": "Sean McGregor, Khoa Lam, AIID"
    }
  ],
  "data_type": "AVID",
  "data_version": "0.2",
  "description": {
    "lang": "eng",
    "value": "Kronos\u2019s scheduling algorithm and its use by Starbucks managers allegedly negatively impacted financial and scheduling stability for Starbucks employees, which disadvantaged wage workers."
  },
  "impact": {
    "avid": {
      "lifecycle_view": [
        "L06: Deployment"
      ],
      "risk_domain": [
        "Performance"
      ],
      "sep_view": [
        "P0401: Psychological Safety",
        "P0403: Socioeconomic safety"
      ],
      "taxonomy_version": "0.2"
    }
  },
  "last_modified_date": "2023-03-30",
  "metadata": {
    "vuln_id": "AVID-2023-V023"
  },
  "problemtype": {
    "classof": "AIID Incident",
    "description": {
      "lang": "eng",
      "value": "Kronos Scheduling Algorithm Allegedly Caused Financial Issues for Starbucks Employees"
    }
  },
  "published_date": "2023-03-30",
  "references": [
    {
      "label": "Incident 10: Kronos Scheduling Algorithm Allegedly Caused Financial Issues for Starbucks Employees",
      "url": "https://incidentdatabase.ai/cite/10"
    }
  ],
  "reports": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.