couch-auth up to 0.21.2 src/user.ts information disclosure

Summaryinfo

A vulnerability marked as problematic has been reported in couch-auth up to 0.21.2. Affected is an unknown function of the file src/user.ts. Performing a manipulation results in information disclosure. This vulnerability is reported as CVE-2025-60794. The attack requires a local approach. No exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, was found in couch-auth up to 0.21.2. This affects an unknown code of the file src/user.ts. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

Session tokens and passwords in couch-auth 0.21.2 are stored in JavaScript objects and remain in memory without explicit clearing in src/user.ts lines 700-707. This creates a window of opportunity for sensitive data extraction through memory dumps, debugging tools, or other memory access techniques, potentially leading to session hijacking.

The advisory is shared at npmjs.com. This vulnerability is uniquely identified as CVE-2025-60794 since 09/26/2025. The exploitability is told to be easy. An attack has to be approached locally. Additional levels of successful authentication are required for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• couch-auth

Version

• 0.21.0
• 0.21.1
• 0.21.2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion