Memory leak in cups `fuzz_ppd` harness
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c
- Domain
- testing-qa
Research direction
Start with the fuzz_ppd harness and the latest pull request linked in the issue, focusing on the ppdsize and cups_options cleanup paths around return 0. Done means the harness handles those allocations safely during termination and is ready for OSS-Fuzz without memory-management false positives.
Written by the indexing model from the issue text.
Description
As mentioned in the latest pull request regarding fuzz_ppd. The current implementation of this harness contains some unhandled variable issues, e.g., ppdsize and cups_options are not properly freed when execution terminates via a return 0 condition during fuzzing.
While the overall functionality of the harness is correct, a reconstruction of this harness is required to ensure proper memory management. So that OSS-Fuzz can focus on identifying real bugs rather than surfacing false positives, which should be addressed before enabling this harness into the OSS-Fuzz fuzzing process.
- Dominant language
- C
- Stars
- 8
- Forks
- 18
- Avg merge
- 7h 37m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenPrinting/fuzzing
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
OpenPrinting/fuzzing#45 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
OpenPrinting/fuzzing#47 · 4 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
OpenPrinting/fuzzing#46 ·
-
Memory allocation/deallocation mismatch in fuzz_array.c causes immediate crash with AddressSanitizer Open
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
OpenPrinting/fuzzing#43 ·
-
good first issue
Difficulty 4/5 3-5 days Newbie friendliness 35/100
OpenPrinting/fuzzing#5 · 1 comment ·
All issues in OpenPrinting/fuzzing
Similar issues
-
internal.h中，漏掉了1个定义。 Open
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zephyrproject-rtos/zephyr#120011 ·