[PR #2046] fix(rust): harden ccxr_process_cc_data against excessive cc_count

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ccextractor#2857

claunia commented

2026-01-29 17:24:16 +00:00

Owner

Original Pull Request: https://github.com/CCExtractor/ccextractor/pull/2046

State: closed
Merged: No

In raising this pull request, I confirm the following (please check boxes):

I have read and understood the contributors guide.
I have checked that another pull request for this purpose does not exist.
I have considered, and confirmed that this submission will be valuable to others.
I accept that this submission may not be used, and the pull request closed at the will of the maintainer.
I give this submission freely, and claim no ownership to its content.
I have mentioned this change in the changelog.

My familiarity with the project is as follows (check one):

I have never used CCExtractor.
I have used CCExtractor just a couple of times.
I absolutely love CCExtractor, but have not contributed previously.
I am an active contributor to CCExtractor.

{pull request content here}

Summary

Adds a defensive upper bound on cc_count in ccxr_process_cc_data to prevent
excessive allocations or misuse at the FFI boundary.

Details

Rejects calls where cc_count exceeds a sane limit
Logs a warning instead of attempting allocation
Adds a unit test to validate the guard
No behavior change for valid inputs

**Original Pull Request:** https://github.com/CCExtractor/ccextractor/pull/2046 **State:** closed **Merged:** No ---  **In raising this pull request, I confirm the following (please check boxes):** - [x] I have read and understood the [contributors guide](https://github.com/CCExtractor/ccextractor/blob/master/.github/CONTRIBUTING.md). - [x] I have checked that another pull request for this purpose does not exist. - [x] I have considered, and confirmed that this submission will be valuable to others. - [x] I accept that this submission may not be used, and the pull request closed at the will of the maintainer. - [x] I give this submission freely, and claim no ownership to its content. - [ ] **I have mentioned this change in the [changelog](https://github.com/CCExtractor/ccextractor/blob/master/docs/CHANGES.TXT).** **My familiarity with the project is as follows (check one):** - [ ] I have never used CCExtractor. - [x] I have used CCExtractor just a couple of times. - [ ] I absolutely love CCExtractor, but have not contributed previously. - [ ] I am an active contributor to CCExtractor. --- {pull request content here} ### Summary Adds a defensive upper bound on `cc_count` in `ccxr_process_cc_data` to prevent excessive allocations or misuse at the FFI boundary. ### Details - Rejects calls where `cc_count` exceeds a sane limit - Logs a warning instead of attempting allocation - Adds a unit test to validate the guard - No behavior change for valid inputs

claunia added the pull-request label 2026-01-29 17:24:16 +00:00

claunia closed this issue

[PR #2046] fix(rust): harden ccxr_process_cc_data against excessive cc_count #2857

Summary

Details