fix:Potential ReDoS Vulnerability or Inefficient Regular Expression in Project: Need for Assessment and Mitigation

[mmmsssttt404]

Steps to reproduce Hello,

I am writing to report a potential Regular Expression Denial of Service (ReDoS) vulnerability or Inefficient Regular Expression in the project. When using specially crafted input strings in the context, it may lead to extremely high CPU usage, application freezing, or denial of service attacks.

Location of Issue:

The vulnerability is related to a regular expression used in the following validation file, which may result in significantly prolonged execution times under certain conditions.

https://github.com/yarnpkg/yarn/blob/7cafa512a777048ce0b666080a24e80aae3d66a9/src/resolvers/exotics/registry-resolver.js#L12

1.git clone https://github.com/mmmsssttt404/yarn.git
2.yarn install
3.yarn test __tests__/resolvers/exotics/hosted-git-resolver.js

use time:

Proposed Solution: Change the regular expression to

https://github.com/mmmsssttt404/yarn/blob/5150f8613c99219a7e4c51d7f2e0c1febed532de/src/resolvers/exotics/registry-resolver.js#L12

Thank you for your attention to this matter. Your evaluation and response to this potential security concern would be greatly appreciated.

Best regards,

Search keywords: ReDoS

[mmmsssttt404]

3.yarn test __tests__/resolvers/exotics/hosted-git-resolver.js this change to yarn test __tests__/resolvers/exotics/registry-resolver.js

[mmmsssttt404]

Benchmarks show clear quadratic growth with input size, not linear. Even at ~100k chars, runtime reaches several seconds. ReDoS does not require exponential blowup — Polynomial behavior is already recognized as exploitable