Pagy Gem I18n Locale Option Vulnerability: Early Warning
An early warning has been issued regarding a potential vulnerability in the Pagy gem where the I18n locale option is not validated before being used in a file path, potentially allowing untrusted input to influence file loading.
What happened
Reportedly, the Pagy gem's I18n locale option is not validated before being incorporated into a file path. This appears to create a scenario where untrusted input could potentially redirect the lookup outside the intended locales directory. The vulnerability is under investigation and has been tracked under the ID GHSA-2XMW-F8J8-WFXC. Affected components include versions of the Pagy gem prior to 43.5.6.
To assess your exposure, check if your application utilizes the Pagy gem and whether the I18n locale option is in use. If so, verify the version of the Pagy gem being used. It is recommended to upgrade to Pagy version 43.5.6 or later to mitigate this vulnerability. For more detailed information, consult the primary source at https://github.com/ddnexus/pagy/security/advisories/GHSA-2xmw-f8j8-wfxc.
Given the severity of this potential vulnerability, it is advised to stay updated with the latest information from the primary sources and apply the recommended mitigations as soon as possible. The exact impact and full details are still under investigation, so further updates should be expected.
How 0Day mitigates this
pagy is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.