Scoped Scans limited to 50 Tickets

[TheRedTerror]

Issue:

The scanner gets stuck when using the --scope feature as pagination seems to break and will not continue scanning the project.

When running scoped scans in the n0s1 scanner, the tool only returns a maximum of 50 results, regardless of how many findings the scope actually contains. Investigation shows that pagination is not functioning, causing the API/UI to stop after the first page of results. This leads to incomplete reporting and inaccurate visibility into secrets, exposures, and misconfigurations across large Confluence/Jira workspaces.

Reproduction Steps:

Configure a scoped scan with more than 50 expected results.

Run the scan via CLI or API.

Observe that only the first 50 results are returned.

Confirm that no pagination tokens or continuation requests are issued.

Requested fix:

Investigate and adjust pagination so that more than 50 tickets can be scanned using specific scopes.

[BoBeR182]

I was using this to bypass #39 by setting the jira scope jql:issue.type != "BRD Project" but this prevents me from scanning more than 50 Jira tickets at once.

[blupants]

@TheRedTerror @BoBeR182 Thank you for reporting the issue. I have created a branch with a fix, and it should be included in the next release (PR 40).

I could replicate the issue by setting --limit 1 to force the pagination for each single item. Unfortunately, I don't have a big Jira instance where I could run exhaustive tests to confirm the fix.

Could you please try to run the fix in your side to confirm it addresses your use case? The branch name for the fix is jira-pagination. Here is a suggestion on how to test it:

python3 -m pip install virtualenv
git clone -b jira-pagination https://github.com/spark1security/n0s1.git
cd n0s1/src/n0s1
python3 -m venv n0s1_python
source n0s1_python/bin/activate
python3 -m pip install -r ../../requirements.txt
python3 n0s1.py jira_scan <YOUR_JIRA_SCAN_ARGUMENTS>
deactivate

Please let me know. Once you confirm the fix works, I will release the new version soon after.

[BoBeR182]

This issue is fixed via the jira-pagination branch.
Confirming over 50 jira tickets were scanned.

[blupants]

Thank you for confirming the fix. It has been deployed to release v1.0.31