CWE
200
Advisory Published
Updated

GHSA-892p-pqrr-hxqr: Infoleak

First published: Fri May 02 2025(Updated: )

## Summary An information disclosure vulnerability affecting Flags SDK has been addressed. It impacted `flags` ≤3.2.0 and `@vercel/flags` ≤3.1.1 and in certain circumstances, allowed a bad actor with detailed knowledge of the vulnerability to list all flags returned by the flags discovery endpoint (`.well-known/vercel/flags`). ## Impact This vulnerability allowed for information disclosure, where a bad actor could gain access to a list of all feature flags exposed through the flags discovery endpoint, including the: - Flag names - Flag descriptions - Available options and their labels (e.g. `true`, `false`) - Default flag values Not impacted: - Flags providers were not accessible No write access nor additional customer data was exposed, this is limited to just the values noted above. Vercel has automatically mitigated this incident on behalf of our customers for the default flags discovery endpoint at `.well-known/vercel/flags`. Flags Explorer will be disabled and show a warning notice until upgraded to `flags@4.0.0`. ## Resolution The `verifyAccess` function was patched within `flags@4.0.0`. Users of `@vercel/flags` should also migrate to `flags@4.0.0`. For further guidance on upgrading your version, please see our [upgrade guide](https://github.com/vercel/flags/blob/main/packages/flags/guides/upgrade-to-v4.md). ## Mitigations Vercel implemented a network-level mitigation to prevent the default flags discovery endpoint at `/.well-known/vercel/flags` being reachable, which automatically protects Vercel deployments against exploitation of this issue. Users need to upgrade to `flags@4.0.0` to re-enable the Flags Explorer. This automatic mitigation is not effective in two scenarios: - When using the Flags SDK on Pages Router, as the original non-rewritten route would still be accessible, e.g. `/api/vercel/flags`. - When using a custom path for the flags discovery endpoint. If you are not protected by the Vercel default mitigation you can temporarily deny access to the other exposed flags discovery endpoints through a custom WAF rule while you upgrade to the latest version. ## References - https://vercel.com/changelog/information-disclosure-in-flags-sdk-cve-2025-46332 - https://github.com/vercel/flags/blob/main/packages/flags/guides/upgrade-to-v4.md

Affected SoftwareAffected VersionHow to fix
npm/@vercel/flags<=3.1.1
npm/flags<=3.2.0
4.0.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of GHSA-892p-pqrr-hxqr?

    GHSA-892p-pqrr-hxqr is considered a moderate severity information disclosure vulnerability.

  • How do I fix GHSA-892p-pqrr-hxqr?

    To fix GHSA-892p-pqrr-hxqr, upgrade to version 4.0.0 or later of the flags package or update to @vercel/flags version higher than 3.1.1.

  • Which versions are affected by GHSA-892p-pqrr-hxqr?

    Versions of flags up to and including 3.2.0 and @vercel/flags up to and including 3.1.1 are affected by GHSA-892p-pqrr-hxqr.

  • What type of vulnerability is GHSA-892p-pqrr-hxqr?

    GHSA-892p-pqrr-hxqr is an information disclosure vulnerability that allows unauthorized access to flags data.

  • Can GHSA-892p-pqrr-hxqr lead to greater security issues?

    Yes, GHSA-892p-pqrr-hxqr can potentially allow attackers to exploit exposed flags data for further attacks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203