Skip to main content
VulnerabilityPublished Updated

CVE-2024-57177: couch-auth · Template Injection

Affects couch-authSource CVE Database V5

0

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Feb 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
npmperfood/couch-authpkg:npm/perfood/couch-authOther threatsAffected
  • <=0.21.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-57177, organizations should first check for updates or patches from the perfood/couch-auth maintainers and apply them promptly once available. In the absence of official patches, developers should implement strict validation and sanitization of the host header values before processing them in any template rendering context. Employing allowlists for acceptable host header values can reduce injection risks. Additionally, refactor the email change confirmation logic to avoid direct injection of untrusted input into templates. Use secure template engines that enforce context-aware escaping and sandboxing to limit SSTI impact. Implement runtime application self-protection (RASP) or web application firewalls (WAF) with rules to detect and block suspicious host header manipulations. Monitor application logs for unusual host header patterns or errors indicative of attempted SSTI exploitation. Conduct code reviews focusing on template rendering and input handling. Finally, educate development teams about secure coding practices related to template injection vulnerabilities.

Description

A host header injection vulnerability exists in the NPM package of perfood/couch-auth <= 0.21.2. By sending a specially crafted host header in the email change confirmation request, it is possible to trigger a SSTI which can be leveraged to run limited commands or leak server-side information

References

Community reviews

Loading reviews…