Potential fix for code scanning alert no. 14: Log injection#89
Merged
Conversation
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Contributor
🔄 Submodule Sync Check✅ All submodules are up to date! Automated check · Runs on PR updates |
Contributor
Version Potential fix for code scanning alert no. 14: Log injection ReleaseNotable Changes
All Commits
Last updated: 2026-05-12T23:54:21Z |
Contributor
🔍 Release Integrity Verification
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Potential fix for https://github.com/TrivaJS/triva/security/code-scanning/14
To fix log injection, sanitize any user-influenced values before writing them to logs by removing carriage returns and newlines (
\r,\n).The best minimal fix here is to sanitize
entry.request.methodandentry.request.urlat the logging point (line ~203), preserving existing behavior while neutralizing log-forging characters.In
lib/middleware/error-tracker.js, update the development logging block:console.error(\Request: ...`)`, create sanitized local variables:''for nullish values).\rand\nusing.replace(/[\r\n]/g, '').entry.request.methodandentry.request.url.No new imports or dependencies are required.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.