CVE-2026-54511
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
Summary
LogTape is an unobtrusive logging library. Prior to 1.3.11, 2.0.14, and 2.1.5, the @logtape/syslog package's escapeStructuredDataValue() function in packages/syslog/src/syslog.ts does not neutralize C0 control characters from U+0000 through U+001F in structured data values, and formatStructuredData() inserts property keys without validating the RFC 5424 SD-NAME grammar. When includeStructuredData is true, an attacker-controlled newline can terminate an RFC 6587 non-transparent TCP syslog frame and make following bytes appear as a forged RFC 5424 record, while a key containing a closing bracket or other forbidden character can terminate or corrupt the structured-data element. Applications that forward attacker-controlled property values or keys can therefore allow forged records with arbitrary hosts, applications, process identifiers, facilities, or severity levels, undermining downstream collector and SIEM integrity. This issue is fixed in versions 1.3.11, 2.0.14, and 2.1.5.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| dahlia | logtape | < 1.3.11 | affected |
| dahlia | logtape | >= 2.0.0, < 2.0.14 | affected |
| dahlia | logtape | >= 2.1.0, < 2.1.5 | affected |
Weaknesses
- CWE-93: CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection')
- CWE-117: CWE-117: Improper Output Neutralization for Logs
References
- https://github.com/dahlia/logtape/security/advisories/GHSA-8h6h-x5pq-56fq
- https://github.com/dahlia/logtape/commit/7a6e5b9ddf7915edfff78fa129bc17c979b2a623
- https://github.com/dahlia/logtape/releases/tag/1.3.11
- https://github.com/dahlia/logtape/releases/tag/2.0.14
- https://github.com/dahlia/logtape/releases/tag/2.1.5
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.