CVE Tools
Track your stack

CVE-2021-23682

Prototype Pollution

Public exploit available. Not confirmed exploited in the wild yet. Fixed versions are out.

CVSS 3.17.3HighEPSS percentile82nd2.1% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
Public exploit: 2 sourcesFix5 products4 fixed builds listed below

Published Updated Sources: CVE.org, NVD, GitHub

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • N/a Litespeed.jsAffected: ≥ unspecified, < 0.3.12Upgrade to: 0.3.12Stated by: CVE record
  • N/a Appwrite/server-ceAffected: ≥ 0.12.0, < unspecifiedUpgrade to: unspecifiedAffected: ≥ unspecified, < 0.12.2Upgrade to: 0.12.2Affected: ≥ unspecified, < 0.11.1Upgrade to: 0.11.1Stated by: CVE record
  • Npm Litespeed.jsAffected: < 0.3.12Upgrade to: 0.3.12Stated by: GitHub advisory
  • Packagist appwrite/server-ceAffected: ≥ 0.12.0, < 0.12.2Upgrade to: 0.12.2Stated by: GitHub advisory
  • AppwriteAffected: < 0.11.1Upgrade to: 0.11.1Stated by: NVD

Versions as the sources state them. 1 more product has version data. Full version matrix after sign-in

Check it yourselfA free Nuclei check exists for this CVE. Run it against your hosts.Is your organisation exposed?Discuss checks for your systems with a specialist. Scope is agreed before testing.

What it is

From the CVE record

This affects the package litespeed.js before 0.3.12; the package appwrite/server-ce from 0.12.0 and before 0.12.2, before 0.11.1. When parsing the query string in the getJsonFromUrl function, the key that is set in the result object is not properly sanitized leading to a Prototype Pollution vulnerability.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS82nd
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

2 sources with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

2.1% chance of exploitation activity in the next 30 days, which ranks it in the 82nd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

The patch came 471 days before any public exploit.

  1. Public exploit / PoCsource: othernuclei check added
  2. Patch availablerecord updated
  3. Publishedweakness classified, att&ck mapped

Affected products

And 2 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

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

Scored 7.3 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 4 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Litespeed.js, not every advisory. This one: public exploit.