GHSA-45qm-j4m9-whv9: Ezsystems/ezplatform EZ Platform CSRF Token Vulnerability

HIGH
Share
CWE-352
Published
Advisory Summary

GHSA-45qm-j4m9-whv9 is a HIGH ez platform csrf token vulnerability (CWE-352: Cross-Site Request Forgery (CSRF)) affecting Ezsystems/ezplatform libraries in the Packagist ecosystem. The issue involves ez platform csrf token in login form is disabled by default. Remediation is available by upgrading affected packages to version 2.5.4.

GHSA-45qm-j4m9-whv9 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-45qm-j4m9-whv9
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-352: Cross-Site Request Forgery (CSRF)
Affected Product Ezsystems/ezplatform
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix GHSA-45qm-j4m9-whv9

To remediate this vulnerability, upgrade all affected Ezsystems/ezplatform dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

ezsystems/ezplatform fixed: 2.5.4 
Upgrade ezsystems/ezplatform to 2.5.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for ezsystems/ezplatform

How to Check if You Are Affected

To determine whether your application is affected by GHSA-45qm-j4m9-whv9, inspect your project dependencies for Ezsystems/ezplatform:

inspect dependencies for ezsystems/ezplatform

Analyze the terminal output to locate any version of Ezsystems/ezplatform in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.5.4), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-352: Cross-Site Request Forgery (CSRF), where the web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. In Ezsystems/ezplatform, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

his security advisory fixes a potential vulnerability in the eZ Platform log in form. That form has a Cross-Site Request Forgery (CSRF) token, but the CSRF functionality is not enabled by default, meaning the token is inactive. The fix is distributed via Composer as ezsystems/ezplatform v2.5.4, and in v3.0.0 when that will be released. If you'd like to manually enable it in your configuration, this is done by editing your app/config/security.yml and setting the "csrf_token_generator" key to "security.csrf.token_manager", like this: ``` security: firewalls: ezpublish_front: form_login: csrf_token_generator: security.csrf.token_manager ``` NB: In eZ Platform 3.0 this file has been moved to config/packages/security.yaml

GHSA-45qm-j4m9-whv9 Affected Ezsystems/ezplatform Versions

1 component(s)
Fixed Versions:
2.5.4
Product / Package Ecosystem Affected Versions Fixed Version
ezsystems/ezplatform
 Packagist
≥ 2.5.0
< 2.5.4
2.5.4

References

Ezsystems/ezplatform Source Repository REPOSITORY
https://github.com/FriendsOfPHP/security-advisories/blob/master/ezsystems/ezplatform/2019-06-27-1.yaml
Ezsystems/ezplatform Source Repository REPOSITORY
https://github.com/ezsystems/ezplatform
Ezsystems/ezplatform Security Information SECURITY
https://share.ez.no/community-project/security-advisories/ezsa-2019-004-csrf-token-in-login-form-is-disabled-by-default
Ezsystems/ezplatform Security Information SECURITY
https://web.archive.org/web/20210614185223/https://share.ez.no/community-project/security-advisories/ezsa-2019-004-csrf-token-in-login-form-is-disabled-by-default

Frequently Asked Questions

What is GHSA-45qm-j4m9-whv9?
GHSA-45qm-j4m9-whv9 is a security vulnerability in Ezsystems/ezplatform involving eZ Platform CSRF token in login form is disabled by default under CWE-352: Cross-Site Request Forgery (CSRF).
Which Ezsystems/ezplatform versions are affected?
Affected versions include releases prior to 2.5.4 across affected packages: ezsystems/ezplatform.
What version fixes GHSA-45qm-j4m9-whv9?
Upgrading to 2.5.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is ezsystems/ezplatform affected?
Yes, ezsystems/ezplatform is affected in releases prior to 2.5.4. Upgrade your dependency to 2.5.4 or later.
What CWE is associated with GHSA-45qm-j4m9-whv9?
GHSA-45qm-j4m9-whv9 is classified under CWE-352: Cross-Site Request Forgery (CSRF) (The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.).
How can I check Packagist dependencies for GHSA-45qm-j4m9-whv9?
Run the dependency tree command: 'inspect dependencies for ezsystems/ezplatform'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-45qm-j4m9-whv9",
  "modified" : "2024-05-15T21:15:21Z",
  "published" : "2024-05-15T21:15:21Z",
  "aliases" : [ ],
  "summary" : "eZ Platform CSRF token in login form is disabled by default",
  "details" : "his security advisory fixes a potential vulnerability in the eZ Platform log in form. That form has a Cross-Site Request Forgery (CSRF) token, but the CSRF functionality is not enabled by default, meaning the token is inactive. The fix is distributed via Composer as ezsystems/ezplatform v2.5.4, and in v3.0.0 when that will be released.\n\nIf you'd like to manually enable it in your configuration, this is done by editing your app/config/security.yml and setting the \"csrf_token_generator\" key to \"security.csrf.token_manager\", like this:\n```\nsecurity:\n    firewalls:\n        ezpublish_front:\n            form_login:\n                csrf_token_generator: security.csrf.token_manager\n```\nNB: In eZ Platform 3.0 this file has been moved to config/packages/security.yaml\n\n",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "ezsystems/ezplatform"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.5.0"
      }, {
        "fixed" : "2.5.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/ezsystems/ezplatform/2019-06-27-1.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/ezsystems/ezplatform"
  }, {
    "type" : "WEB",
    "url" : "https://share.ez.no/community-project/security-advisories/ezsa-2019-004-csrf-token-in-login-form-is-disabled-by-default"
  }, {
    "type" : "WEB",
    "url" : "https://web.archive.org/web/20210614185223/https://share.ez.no/community-project/security-advisories/ezsa-2019-004-csrf-token-in-login-form-is-disabled-by-default"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-352" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-05-15T21:15:21Z",
    "nvd_published_at" : null
  }
}