github-starred/libxlsxwriter

Fork 0

mirror of https://github.com/jmcnamara/libxlsxwriter.git synced 2026-05-15 14:15:54 -06:00

[GH-ISSUE #418] OSSFuzz integration #329

New issue

Closed

opened 2026-05-05 12:09:29 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 12:09:29 -06:00

Owner

Originally created by @capuanob on GitHub (Nov 12, 2023).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/418

Hello,

I worked with @ennamarie19 in the OSS-Fuzz integration for the Python API to XlsxWriter (here. I was wondering if you would be open to a harness being developed and proposed to the OSS-Fuzz committee for the C API as well. If so, I will handle the integration and development of the harness. Would you like the same e-mail used for any defects / bugs discovered in the fuzzing process?

Thank you for your consideration!

Originally created by @capuanob on GitHub (Nov 12, 2023). Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/418 Hello, I worked with @ennamarie19 in the OSS-Fuzz integration for the Python API to XlsxWriter ([here](https://github.com/jmcnamara/XlsxWriter/pull/1030). I was wondering if you would be open to a harness being developed and proposed to the OSS-Fuzz committee for the C API as well. If so, I will handle the integration and development of the harness. Would you like the same e-mail used for any defects / bugs discovered in the fuzzing process? Thank you for your consideration!

gitea-mirror closed this issue

2026-05-05 12:09:31 -06:00

gitea-mirror commented

2026-05-05 12:09:35 -06:00

Author

Owner

@jmcnamara commented on GitHub (Nov 13, 2023):

Hi.

Yes I am fine with that. You can use the same email address. Try to use the dev directory again if possible.

Thanks for the effort.

BTW, has there been any issues flagged in the Python version yet? I didn't get any emails.

@jmcnamara commented on GitHub (Nov 13, 2023): Hi. Yes I am fine with that. You can use the same email address. Try to use the dev directory again if possible. Thanks for the effort. BTW, has there been any issues flagged in the Python version yet? I didn't get any emails.

gitea-mirror commented

2026-05-05 12:09:36 -06:00

Author

Owner

@capuanob commented on GitHub (Nov 14, 2023):

@jmcnamara Thank you very much! I'll be sure to use the dev directory and keep instrumentation optional in the build system.

As for bugs, nothing has popped yet. On that note, do you have any ideas for new, potential entry-points for testing that we could add to increase coverage and uncover bugs?

@capuanob commented on GitHub (Nov 14, 2023): @jmcnamara Thank you very much! I'll be sure to use the dev directory and keep instrumentation optional in the build system. As for bugs, nothing has popped yet. On that note, do you have any ideas for new, potential entry-points for testing that we could add to increase coverage and uncover bugs?

gitea-mirror commented

2026-05-05 12:09:37 -06:00

Author

Owner

@jmcnamara commented on GitHub (Nov 15, 2023):

@capuanob

This is probably a question I should have asked earlier but what are your motivations and goals for doing this work?

@jmcnamara commented on GitHub (Nov 15, 2023): @capuanob This is probably a question I should have asked earlier but what are your motivations and goals for doing this work?

gitea-mirror commented

2026-05-05 12:09:38 -06:00

Author

Owner

@capuanob commented on GitHub (Nov 16, 2023):

I studied cybersecurity with a focus in binary exploitation and became
familiar with fuzz-testing in that process. I’m interested in a future
career working in fuzzing, so I contribute to OSSFuzz in my free time for
open-sourced projects to build up a portfolio and experience.

Thank You, Bailey Capuano

@capuanob commented on GitHub (Nov 16, 2023): I studied cybersecurity with a focus in binary exploitation and became familiar with fuzz-testing in that process. I’m interested in a future career working in fuzzing, so I contribute to OSSFuzz in my free time for open-sourced projects to build up a portfolio and experience. Thank You, Bailey Capuano

gitea-mirror commented

2026-05-05 12:09:39 -06:00

Author

Owner

@jmcnamara commented on GitHub (Nov 16, 2023):

@capuanob That is cool. You will probably have better luck fuzzing this C based project (although I have used a reasonable amount of defensive programming). If you contact me offline I can suggest some attack surfaces: jmcnamara @ cpan.org

@jmcnamara commented on GitHub (Nov 16, 2023): @capuanob That is cool. You will probably have better luck fuzzing this C based project (although I have used a reasonable amount of defensive programming). If you contact me offline I can suggest some attack surfaces: jmcnamara @ cpan.org

gitea-mirror commented

2026-05-05 12:09:40 -06:00

Author

Owner

@capuanob commented on GitHub (Nov 17, 2023):

@jmcnamara Thank you very much! I reached out to you

@capuanob commented on GitHub (Nov 17, 2023): @jmcnamara Thank you very much! I reached out to you