Advisory Database
  • Advisories
  • Dependency Scanning
  1. composer
  2. ›
  3. cuyz/valinor
  4. ›
  5. GMS-2022-563

GMS-2022-563: Automatic named constructor discovery

April 1, 2022 (updated April 5, 2022)

The issue arises when upgrading from cuyz/valinor:0.3.0 to a newer system on an existing application, which broke due to the wrong constructor being picked. The bigger security concern is akin to https://github.com/rails/rails/issues/5228.

References

  • github.com/CuyZ/Valinor/commit/718d3c1bc2ea7d28b4b1f6c062addcd1dde8660b
  • github.com/CuyZ/Valinor/releases/tag/0.7.0
  • github.com/CuyZ/Valinor/security/advisories/GHSA-xhr8-mpwq-2rr2
  • github.com/advisories/GHSA-xhr8-mpwq-2rr2

Code Behaviors & Features

Detect and mitigate GMS-2022-563 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions starting from 0.5.0 before 0.7.0

Fixed versions

  • 0.7.0

Solution

Upgrade to version 0.7.0 or above.

Source file

packagist/cuyz/valinor/GMS-2022-563.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 14 May 2025 12:14:34 +0000.