How severe is CVE-2013-3300?

No CVSS score has been assigned to CVE-2013-3300 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-3300?

CVE-2013-3300 affects the following packages: net.liftweb:lift-webkit (Maven), net.liftweb:lift-webkit_2.7.7 (Maven), net.liftweb:lift-webkit_2.8.0 (Maven), net.liftweb:lift-webkit_2.8.1 (Maven), net.liftweb:lift-webkit_2.8.2 (Maven), net.liftweb:lift-webkit_2.9.0 (Maven), net.liftweb:lift-webkit_2.9.0-1 (Maven), net.liftweb:lift-webkit_2.9.1 (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-3300?

A fix is available for CVE-2013-3300; check the affected-versions list above or the advisory for the patched release of net.liftweb:lift-webkit, then make sure no transitive dependency still pins the vulnerable range.

How do I detect CVE-2013-3300 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.liftweb:lift-webkit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-3300 if there is no patch (or I can't update yet)?

Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Is CVE-2013-3300 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2013-3300, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-3300?

CVE-2013-3300 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-3300?

CVE-2013-3300 is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2013-3300 published, and has it been updated?

CVE-2013-3300 was published on May 17, 2022 and was last updated on September 30, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2013-3300 — lift-webkit

Fix: lift/framework@099d9c8

CVE-2013-3300 is a Buffer Overflow vulnerability in net.liftweb:lift-webkit. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for net.liftweb:lift-webkit — see the affected versions and patch details below.

Lift Sensitive Information Disclosure

Published

May 17, 2022

Updated

Sep 30, 2025

Affected

8 pkgs

Patched

1 / 8

Exploits

2 known

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

8 pkgs affected

☕net.liftweb:lift-webkit☕net.liftweb:lift-webkit_2.7.7☕net.liftweb:lift-webkit_2.8.0☕net.liftweb:lift-webkit_2.8.1☕net.liftweb:lift-webkit_2.8.2☕net.liftweb:lift-webkit_2.9.0☕net.liftweb:lift-webkit_2.9.0-1☕net.liftweb:lift-webkit_2.9.1

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The JsonParser class in json/JsonParser.scala in Lift before 2.5 interprets a certain end-index value as a length value, which allows remote authenticated users to obtain sensitive information from other users' sessions via invalid input data containing a < (less than) character.

Affected Packages

8 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`net.liftweb:lift-webkit`	all versions	No fix
☕Maven	`net.liftweb:lift-webkit_2.7.7`	all versions	No fix
☕Maven	`net.liftweb:lift-webkit_2.8.0`	all versions	No fix
☕Maven	`net.liftweb:lift-webkit_2.8.1`	all versions	No fix
☕Maven	`net.liftweb:lift-webkit_2.8.2`	all versions	No fix
☕Maven	`net.liftweb:lift-webkit_2.9.0`	all versions	No fix

Affected Products

1 product · 11 configurations

Application

liftliftweb

≤ 2.5

5 versions

2.12.22.32.42.5

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The JsonParser class in json/JsonParser.scala in Lift before 2.5 interpr…

github.comNVDJul 2013

Report on blog.addepar.com

blog.addepar.comNVDJul 2013

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.liftweb:lift-webkit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2013-3300; check the affected-versions list above or the advisory for the patched release of net.liftweb:lift-webkit, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.