fix(deps): update dependency @octokit/plugin-paginate-rest to v9 [security] #161
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.
This PR contains the following updates:
^6.1.2
->^9.0.0
GitHub Vulnerability Alerts
CVE-2025-25288
Summary
For the npm package
@octokit/plugin-paginate-rest
, when callingoctokit.paginate.iterator()
, a specially craftedoctokit
instance—particularly with a maliciouslink
parameter in theheaders
section of therequest
—can trigger a ReDoS attack.Details
The issue occurs at line 39 of iterator.ts in the @octokit/plugin-paginate-rest repository. The relevant code is as follows:
The regular expression
/<([^>]+)>;\s*rel="next"/
may lead to a potential backtracking vulnerability, resulting in a ReDoS (Regular Expression Denial of Service) attack. This could cause high CPU utilization and even service slowdowns or freezes when processing specially craftedLink
headers.PoC
The gist of PoC.js
result:
Impact
What kind of vulnerability is it?
This is a Regular Expression Denial of Service (ReDoS) vulnerability, which occurs due to excessive backtracking in the regex pattern:
/<([^>]+)>;\s*rel="next"/
When processing a specially crafted
Link
header, this regex can cause significant performance degradation, leading to high CPU utilization and potential service unresponsiveness.Who is impacted?
@octokit/plugin-paginate-rest
who calloctokit.paginate.iterator()
and process untrusted or manipulatedLink
headers.Release Notes
octokit/plugin-paginate-rest.js (@octokit/plugin-paginate-rest)
v9.2.2
Compare Source
Bug Fixes
v9.2.1
Compare Source
Bug Fixes
@octokit/core
peerDependency to v5 (#599) (5b84386)v9.2.0
Compare Source
Features
/orgs/{org}/organization-roles/{role_id}/teams
and/orgs/{org}/organization-roles/{role_id}/users
endpoints (#594) (75aeaaf)v9.1.5
Compare Source
Bug Fixes
v9.1.4
Compare Source
Bug Fixes
@octokit/types
(#575) (27db9ae)v9.1.3
Compare Source
Bug Fixes
@octokit/types
(#574) (0940cb7)v9.1.2
Compare Source
Bug Fixes
v9.1.1
Compare Source
Bug Fixes
v9.1.0
Compare Source
Features
GET /orgs/{org}/properties/values
,GET /orgs/{org}/rulesets/rule-suites
,GET /repos/{owner}/{repo}/rulesets/rule-suites
endpoints (#569) (4b8d674)v9.0.0
Compare Source
Features
BREAKING CHANGES
v8.0.0
Compare Source
chore
BREAKING CHANGES
@octokit/core
to v5@octokit/types
to v11v7.1.2
Compare Source
Bug Fixes
v7.1.1
Compare Source
Bug Fixes
v7.1.0
Compare Source
Features
v7.0.0
Compare Source
Continuous Integration
BREAKING CHANGES
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.