Skip to main content
Public proof of conceptFix available

CVE-2024-3429

A public proof of concept exists; no exploitation attested.

  • Published2024-06-06
  • Fixed in9.6
  • WeaknessCWE-22 · CWE-29

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A path traversal vulnerability exists in the parisneo/lollms application, specifically within the `sanitize_path_from_endpoint` and `sanitize_path` functions in `lollms_core\lollms\security.py`. This vulnerability allows for arbitrary file reading when the application is running on Windows. The issue arises due to insufficient sanitization of user-supplied input, enabling attackers to bypass the path traversal protection mechanisms by crafting malicious input. Successful exploitation could lead to unauthorized access to sensitive files, information disclosure, and potentially a denial of service (DoS) condition by including numerous large or resource-intensive files. This vulnerability affects the latest version prior to 9.6.

Timeline

dates in UTC
  1. 2024-06-0619:16CVE publishedNVD

Versions per branch

NVD · OSV · CISA-ADP
Lollms
BranchAffectedFixed in
9.6< 9.69.6
lollms
BranchAffectedFixed in
9.5< 9.5.09.5.0
Parisneo lollms-webui
BranchAffectedFixed in
9.6< 9.69.6

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As @huntr_ai, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • parisneo/lollms
    Affected
    • < 9.6fixed in 9.6custom

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-06-06

Fix

  1. Update Lollms to 9.6

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionpoc2024-06-10
  • NVDCVSS 3.19.8read 2026-10-23
  • CNACVSS 3.09.8known since 2026-10-23
  • CNAweakness (CWE)CWE-29known since 2026-10-23
  • NVDweakness (CWE)CWE-22read 2026-10-23
  • FIRST EPSSEPSS score28.3 %read 2026-11-09
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2024-09-13

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2024-06-06
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-3x47-w4rx-6pm7

Frequently asked questions

What is CVE-2024-3429?

A path traversal vulnerability exists in the parisneo/lollms application, specifically within the `sanitize_path_from_endpoint` and `sanitize_path` functions in `lollms_core\lollms\security.py`. This vulnerability allows for arbitrary file reading when the application is running on Windows. The issue arises due to insufficient sanitization of user-supplied input, enabling attackers to bypass the path traversal protection mechanisms by crafting malicious input. Successful exploitation could lead to unauthorized access to sensitive files, information disclosure, and potentially a denial of service (DoS) condition by including numerous large or resource-intensive files. This vulnerability affects the latest version prior to 9.6.

Is CVE-2024-3429 actively exploited?

A proof-of-concept exploit exists for CVE-2024-3429, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2024-3429?

CVE-2024-3429 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running lollms? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record