Open
Conversation
fix(config): replace vulnerable args regex split with safe tokenizer while preserving Unitech#6031-compatible parsing behavior
|
|
lab-kolerr
pushed a commit
to Kolerr-Lab/SENTINELI-COBOL-KNOWLEDGE-GRAPH
that referenced
this pull request
Feb 27, 2026
Applied fix from PR #6079 which replaces regex-based parsing with tokenizer. RESOLVED: - pm2 Regular Expression Denial of Service (CVE-2025-5891) - Severity: Low (CVSS 2.1/10) - Source: github:dbankier/pm2#master (commit 3c58b3aa) - Fix: Tokenizer-based parser replaces vulnerable regex VERIFICATION: - tokenizePm2ConfigArrayString() function present in code - PR #6079: Unitech/pm2#6079 - Addresses issues from PR #5971 NOTE: npm audit will continue showing this vulnerability because it checks version numbers (6.0.14), not actual code. The fix IS applied in our codebase. Will switch to official release when available. FILES: - package.json: Use github:dbankier/pm2#master - package-lock.json: Lock to commit 3c58b3aa - SECURITY_ADVISORY.md: Updated status to RESOLVED
lab-kolerr
pushed a commit
to Kolerr-Lab/SENTINELI-COBOL-KNOWLEDGE-GRAPH
that referenced
this pull request
Feb 27, 2026
Applied fix from PR #6079 which replaces regex-based parsing with tokenizer. RESOLVED: - pm2 Regular Expression Denial of Service (CVE-2025-5891) - Severity: Low (CVSS 2.1/10) - Source: github:dbankier/pm2#master (commit 3c58b3aa) - Fix: Tokenizer-based parser replaces vulnerable regex VERIFICATION: - tokenizePm2ConfigArrayString() function present in code - PR #6079: Unitech/pm2#6079 - Addresses issues from PR #5971 NOTE: npm audit will continue showing this vulnerability because it checks version numbers (6.0.14), not actual code. The fix IS applied in our codebase. Will switch to official release when available. FILES: - package.json: Use github:dbankier/pm2#master - package-lock.json: Lock to commit 3c58b3aa - SECURITY_ADVISORY.md: Updated status to RESOLVED
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
2 participants
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.
I fixed the above GHSA issue by removing the regex usage and replacing it with a tokeniser.
I also added a number of automated test to so that you do not run into the issue you faced with the other previous attempts.
Input/output should now be matching the existing solution.