The update module should not crash with releases that contain invalid values for core_version_requirement

Created on 1 June 2024, 4 months ago
Updated 18 June 2024, 3 months ago

This issue was reported privately, but has been approved for public discussion by the Drupal Security Team.

Problem/Motivation

The update module does not sufficiently check if core_version_requirement is a valid version constraint.

Steps to reproduce

  1. Install a module.
  2. Issue an updated version of the module with an invalid version number in core_version_requirement in the .info.yml file.
  3. Not needed - the existence of the broken release in the updates.d.o release history feed triggers the bug

Proposed resolution

The following was proposed by @MegaphoneJon.

The update module should be checking its inputs rather than accepting them as-is from d.o. And arguably the release process on d.o should be checking for invalid version constraints.

Remaining tasks

  1. Add tests
  2. Reviews / refinements

User interface changes

None.

API changes

None.

Data model changes

None.

Release notes snippet

TBD

πŸ› Bug report
Status

Fixed

Version

10.2 ✨

Component
UpdateΒ  β†’

Last updated 5 days ago

  • Maintained by
  • πŸ‡ΊπŸ‡ΈUnited States @tedbow
  • πŸ‡ΊπŸ‡ΈUnited States @dww
Created by

πŸ‡¦πŸ‡ΊAustralia mingsong πŸ‡¦πŸ‡Ί

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024