Login timing attack in ezsystems/ezplatform-kernel
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (ezsystems/ezplatform-kernel 1.3.19), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist ezsystems/ezplatform-kernel
- Affected
- >= 1.3.0, < 1.3.19
- Fixed in
- 1.3.19
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-342c-vcff-2ff2 lists affected ranges: Packagist ezsystems/ezplatform-kernel >=1.3.0 <1.3.19
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Ibexa DXP is using random execution time to hinder timing attacks against user accounts, a method of discovering whether a given account exists in a system without knowing its password, thus affecting privacy. This implementation was found to not be good enough in some situations. The fix replaces this with constant time functionality, configured in the new security.yml parameter 'ibexa.security.authentication.constantauthtime'. It will log a warning if the constant time is exceeded. If this happens the setting should be increased.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-342c-vcff-2ff2
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-342c-vcff-2ff2 Advisory: Login timing attack in ezsystems/ezplatform-kernel IDs: GHSA-342c-vcff-2ff2 Record: https://patchnext.com/advisories/ghsa-342c-vcff-2ff2 (revision 1, source checked 26 Oct 2026, 13:56 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: ezsystems/ezplatform-kernel 1.3.19. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist ezsystems/ezplatform-kernel: affected >= 1.3.0, < 1.3.19; fixed in 1.3.19 ## Suggested inspection (read-only) - Packagist ezsystems/ezplatform-kernel: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on ezsystems/ezplatform-kernel. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-342c-vcff-2ff2 (GitHub-reviewed advisory GHSA-342c-vcff-2ff2 lists affected ranges: Packagist ezsystems/ezplatform-kernel >=1.3.0 <1.3.19) Commands are suggestions: review each one before running it.
Loading voting…