Drupal release metadata can attach the literal "Insecure" Release type term to a core release row
Reviewed Drupal Knowledge trusted knowledge, reviewed by a human against authoritative sources
A human reviewed this against registered authoritative sources. It states something about Drupal, not about any one project.
SOURCE FACT: the Drupal update-status release-history feed can attach a Release type taxonomy term whose literal value is "Insecure" to an individual Drupal core release row. PROJECT JOIN: a future finding evaluator may match this only when the Project Analyzer observed installed Drupal core version matches that exact release row in the canonical reviewed release lifecycle context. DRUPAL SEMANTICS (reviewed): For Drupal Update Manager release metadata, a release carrying Release type "Insecure" is treated as insecure; when that exact release is installed, Drupal assigns NOT_SECURE status, whose documented meaning is that the project is missing security update(s). LIMITS: this reviewed meaning does not establish an exploit path, a specific CVE identifier, a finding severity level, or any compromise claim about a project.
Record drupal.update.core-release-insecure-term-condition
What this is
- What is this
- trusted knowledge, reviewed by a human against authoritative sources: Drupal release metadata can attach the literal "Insecure" Release type term to a core release row
- Why it exists
- A human reviewed authoritative Drupal sources and recorded this as trusted knowledge.
- What makes it authoritative
- A human reviewed this against registered authoritative sources. It states something about Drupal, not about any one project.
- Project scope
- Nothing: this record is about Drupal, not about any one project.
- Recommended next step
- Read the record's own actions and checks.
- Was anything changed
- No. Querying Drupal Knowledge changes nothing.
What is not known
- Nothing was left unstated by this record.
What the record states
| Domains | update, core |
|---|---|
| Kind | version-change |
| Version applicability | drupal_core: [{'constraint': 'release-history', 'notes': 'Applies only to an exact release row present in the canonical reviewed release lifecycle context.', 'status': 'applicable'}], notes: Release rows are matched literally and exactly; no branch, range, or ordering inference is authorized. |
Provenance
This record's authority is internal to Drupal Knowledge; no external source snapshot stands behind it.
- authoritative_source · drupal-core-releases · /project/releases/release/terms/term where name is 'Release type' and value is 'Insecure'
https://www.drupal.org/project/drupal/releases - authoritative_source · drupal-update-project-release-semantics · ProjectRelease::isInsecure() returns isReleaseType('Insecure'); createFromArray reads terms['Release type']
https://api.drupal.org/api/drupal/core%21modules%21update%21src%21ProjectRelease.php/class/ProjectRelease/11.x - authoritative_source · drupal-update-status-security-semantics · update_calculate_project_update_status(): existing_version === version and isInsecure() sets UpdateManagerInterface::NOT_SECURE; later branches return early once status is set
https://api.drupal.org/api/drupal/core%21modules%21update%21update.compare.inc/function/update_calculate_project_update_status/11.x - authoritative_source · drupal-update-manager-interface-semantics · UpdateManagerInterface::NOT_SECURE docblock: Project is missing security update(s).
https://api.drupal.org/api/drupal/core%21modules%21update%21src%21UpdateManagerInterface.php/interface/UpdateManagerInterface/11.x
Related records
Only relationships the canonical records already declare. Nothing here is inferred.