{"answers":{"affected":"2 open source packages ship an affected version, including ezsystems/ezpublish-kernel.","exploited":"There is no known exploitation of GHSA-xfqg-p48g-hh94 in the wild and no public exploit code.","fix":"Upgrade ezsystems/ezpublish-kernel to 7.5.29 or later.","what":"GHSA-xfqg-p48g-hh94 is a vulnerability in ezsystems/ezpublish-kernel, published on 2 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-xfqg-p48g-hh94 and fix it if it is affected.\n\nWhat it is: GHSA-xfqg-p48g-hh94 is a vulnerability in ezsystems/ezpublish-kernel, published on 2 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-xfqg-p48g-hh94 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ezsystems/ezpublish-kernel (Packagist): affected from 7.5.0; fixed in 7.5.29\n- ezsystems/ezpublish-kernel (Packagist): affected from 7.5.0; fixed in 7.5.29\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-xfqg-p48g-hh94/ (Markdown: https://insights.sbomify.com/GHSA-xfqg-p48g-hh94/index.md)","id":"GHSA-xfqg-p48g-hh94","markdown":"https://insights.sbomify.com/GHSA-xfqg-p48g-hh94/index.md","name":"GHSA-xfqg-p48g-hh94","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Ibexa DXP","requires_auth":"none","summary":"Attackers can discover valid user accounts via timing attacks due to insufficient randomization in Ibexa DXP login processes.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.constant_auth_time'. It will log a warning if the constant time is exceeded. If this happens the setting should be increased.","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Login timing attack in ezsystems/ezpublish-kernel","id":"GHSA-xfqg-p48g-hh94","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["7.5.29"],"introduced":["7.5.0"],"last_affected":[],"package":"ezsystems/ezpublish-kernel","purl":null,"source":"GHSA-xfqg-p48g-hh94"},{"ecosystem":"Packagist","fixed":["7.5.29"],"introduced":["7.5.0"],"last_affected":[],"package":"ezsystems/ezpublish-kernel","purl":"pkg:composer/ezsystems/ezpublish-kernel","source":"GHSA-xfqg-p48g-hh94"}],"products":null,"published":"2022-06-02","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can discover valid user accounts via timing attacks due to insufficient randomization in Ibexa DXP login processes.","url":"https://insights.sbomify.com/GHSA-xfqg-p48g-hh94/"}