Advisory record · GHSA-jf9v-fxfq-wm76

Lift Sensitive Information Disclosure

No CVSS scoreEPSS 0.015 · 74th percentile

Published by the GitHub Advisory Database at 17 May 2022, 05:07 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
net.liftweb:lift-webkitMavenall versionsNo fixed version yet
net.liftweb:lift-webkit_2.7.7Mavenall versionsNo fixed version yet
net.liftweb:lift-webkit_2.8.0Mavenall versionsNo fixed version yet
net.liftweb:lift-webkit_2.8.1Mavenall versionsNo fixed version yet
net.liftweb:lift-webkit_2.8.2Mavenall versionsNo fixed version yet
net.liftweb:lift-webkit_2.9.0Mavenall versionsNo fixed version yet
net.liftweb:lift-webkit_2.9.0-1Mavenall versionsNo fixed version yet
net.liftweb:lift-webkit_2.9.1Maven<2.52.5
Identifiers
GHSA-jf9v-fxfq-wm76 · CVE-2013-3300
Weakness (CWE)
CWE-119
Published
17 May 2022
Updated
30 Sept 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Lift (net.liftweb:lift-webkit) before 2.5 has a JsonParser flaw that treats an end-index value as a length. A remote authenticated user can send invalid input containing a < character to obtain other users' session data. Upgrade lift-webkit_2.9.1 to 2.5; no fixed version is listed for the other artifacts.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS 0.015, the 74th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:10 UTC First seen by agentprime
  2. 31 Oct 2026, 15:10 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.