Skip to content

← Public intelligence

Packagist package

ezsystems/ezplatform-rest

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratedPackagistPublished

    User can obtain JWT token even if account is disabled

    GHSA-36mj-6r7r-mqhf

    Affected
    • Packagist ezsystems/ezplatform-rest >= 1.3.0, < 1.3.8
    Fixed in
    1.3.8· Vendor fix available
    Issue
    Users can authenticate this way even if their user account is disabled. This is a high risk vulnerability when account disabling is used to block users' access to the system. (Someone who never had an account cannot exploit this vulnerability.) The fix ensures tokens are generated only for enabled user accounts, and is distributed via Composer as ezsystems/ezplatform-rest v1.3.8

    Recommended action: Upgrade to 1.3.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. UnratedPackagistPublished

    /user/sessions endpoint allows detecting valid accounts

    GHSA-7vwg-39h8-8qp8

    Affected
    • Packagist ezsystems/ezplatform-rest >= 1.2.0, <= 1.2.2.0; >= 1.3.0, <= 1.3.1.0
    Fixed in
    1.3.1.11.2.2.1· Vendor fix available
    Issue
    This Security Advisory is about a vulnerability in eZ Platform v1.13, v2.5, and v3.2, and in Ibexa DXP and Ibexa Open Source v3.3. The /user/sessions endpoint can let an attacker detect if a given username or email refers to a valid account. This can be detected through differences in the response data or response time of certain requests. The fix ensures neither attack is possible. The fix is distributed via Composer. If you come across a security issue in our products, here is how you can report it to us: https://doc.ibexa.co/en/latest/guide/reportingissues/#toc

    Recommended action: Upgrade to 1.3.1.1 or 1.2.2.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →