dbcve.org
Switcher ClientApplication · Switcherapi

CVE-2023-23925

HIGH · 7.5 CVSS v3.1 Published 2023-02-03
Fix available
A fix is available. Upgrade to 3.1.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Switcher Client is a JavaScript SDK to work with Switcher API which is cloud-based Feature Flag. Unsanitized input flows into Strategy match operation (EXIST), where it is used to build a regular expression. This may result in a Regular expression Denial of Service attack (reDOS). This issue has been patched in version 3.1.4. As a workaround, avoid using Strategy settings that use REGEX in conjunction with EXIST and NOT_EXIST operations.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Switcher Client JavaScript SDK (versions before 3.1.4) has a reDOS vulnerability where unsanitized user input flows into the Strategy match operation labeled EXIST. This input is directly used to construct a regular expression without proper sanitization, allowing an attacker to provide specially crafted input that causes catastrophic backtracking and denial of service.

MitigationUpgrade to version 3.1.4 or later which contains the patch. As a temporary workaround, avoid using Strategy settings that combine REGEX type with EXIST or NOT_EXIST operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Switcher ClientApplication
Affected:< 3.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed version of Switcher Client JavaScript SDK
    Locate the package.json file for the Switcher Client SDK in your node_modules or project dependencies. Look for the 'version' field under 'switcher-client' or similar package name.
    Affected if The installed version is earlier than 3.1.4 (e.g., 3.1.3, 3.1.0, 2.x.x)
  2. Identify usage of Strategy match operations
    Search your codebase for imports and usage of the Strategy class from the Switcher Client SDK. Look for code that instantiates Strategy objects with operation types.
    Affected if Your code creates Strategy objects with the 'EXIST' or 'NOT_EXIST' operation labels
  3. Check for REGEX type combined with EXIST/NOT_EXIST operations
    Review the Strategy object configurations in your code. Look for instances where the Strategy is configured with 'type' set to 'REGEX' while using 'EXIST' or 'NOT_EXIST' as the operation.
    Affected if A Strategy object has type REGEX and operation EXIST or NOT_EXIST simultaneously
  4. Trace user input into Strategy match operations
    Audit the code paths where user-provided input (request parameters, body data, query strings) is passed as input to the Strategy.match() method or equivalent function.
    Affected if Unsanitized user-controlled strings are passed directly to the match operation without validation or escaping

You are affected if your installed Switcher Client SDK version is below 3.1.4 AND your code uses Strategy with REGEX type combined with EXIST/NOT_EXIST operations where user input flows into the match without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1.4 or later
Fixed in 3.1.4
Interim mitigation

Upgrade to version 3.1.4 or later which contains the patch. As a temporary workaround, avoid using Strategy settings that combine REGEX type with EXIST or NOT_EXIST operations.

Recommended fix High confidence

3.1.4

  1. Check current installed version by reviewing package.json or running `npm list switcher-client`
  2. Upgrade to version 3.1.4 using your package manager: `npm install [email protected]` or `yarn add [email protected]`
  3. Verify the upgrade was successful by checking the installed version with `npm list switcher-client`
  4. If using REGEX in Strategy settings with EXIST or NOT_EXIST operations, test that the fix properly sanitizes input before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Switcher Client Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23925 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-23925 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data