# CVE-2013-3300: Lift Sensitive Information Disclosure > Remote authenticated users can obtain sensitive information from other users' sessions via invalid input data in the Lift JsonParser. - **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Jul 2013 - **Updated:** 17 Sep 2024 - **Also known as:** GHSA-jf9v-fxfq-wm76 ## What is CVE-2013-3300? CVE-2013-3300 is a medium-severity vulnerability in n/a, published on 26 Jul 2013. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2013-3300? 16 open source packages ship an affected version, including net.liftweb:lift-webkit, net.liftweb:lift-webkit_2.7.7 and net.liftweb:lift-webkit_2.8.0. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `net.liftweb:lift-webkit` | Maven | All versions | None | | `net.liftweb:lift-webkit` | Maven | All versions | None | | `net.liftweb:lift-webkit_2.7.7` | Maven | All versions | None | | `net.liftweb:lift-webkit_2.7.7` | Maven | All versions | None | | `net.liftweb:lift-webkit_2.8.0` | Maven | All versions | None | | `net.liftweb:lift-webkit_2.8.0` | Maven | All versions | None | | `net.liftweb:lift-webkit_2.8.1` | Maven | All versions | None | | `net.liftweb:lift-webkit_2.8.1` | Maven | All versions | None | | `net.liftweb:lift-webkit_2.8.2` | Maven | All versions | None | | `net.liftweb:lift-webkit_2.8.2` | Maven | All versions | None | | `net.liftweb:lift-webkit_2.9.0` | Maven | All versions | None | | `net.liftweb:lift-webkit_2.9.0` | Maven | All versions | None | | `net.liftweb:lift-webkit_2.9.0-1` | Maven | All versions | None | | `net.liftweb:lift-webkit_2.9.0-1` | Maven | All versions | None | | `net.liftweb:lift-webkit_2.9.1` | Maven | All versions | 2.5 | | `net.liftweb:lift-webkit_2.9.1` | Maven | All versions | 2.5 | Products: Liftweb Lift. ## How do I fix CVE-2013-3300? Upgrade to a fixed version. ## Is CVE-2013-3300 being exploited? There is no known exploitation of CVE-2013-3300 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2013-3300 and fix it if it is affected. What it is: CVE-2013-3300 is a medium-severity vulnerability in n/a, published on 26 Jul 2013. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2013-3300 in the wild and no public exploit code. Affected packages and fixed versions: - net.liftweb:lift-webkit (Maven): affected all versions; no fix listed - net.liftweb:lift-webkit (Maven): affected all versions; no fix listed - net.liftweb:lift-webkit_2.7.7 (Maven): affected all versions; no fix listed - net.liftweb:lift-webkit_2.7.7 (Maven): affected all versions; no fix listed - net.liftweb:lift-webkit_2.8.0 (Maven): affected all versions; no fix listed - net.liftweb:lift-webkit_2.8.0 (Maven): affected all versions; no fix listed - net.liftweb:lift-webkit_2.8.1 (Maven): affected all versions; no fix listed - net.liftweb:lift-webkit_2.8.1 (Maven): affected all versions; no fix listed - net.liftweb:lift-webkit_2.8.2 (Maven): affected all versions; no fix listed - net.liftweb:lift-webkit_2.8.2 (Maven): affected all versions; no fix listed - net.liftweb:lift-webkit_2.9.0 (Maven): affected all versions; no fix listed - net.liftweb:lift-webkit_2.9.0 (Maven): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2013-3300/ (Markdown: https://insights.sbomify.com/CVE-2013-3300/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2013-3300 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-3300 - OSV: https://osv.dev/vulnerability/CVE-2013-3300 --- From sbomify Insights: https://insights.sbomify.com/CVE-2013-3300/ Summaries are generated and may contain mistakes; the official description above is the record.