Security contact for reproducible memory-safety issues in InstallShield header parsing

[damseleng]

Hello,

I have identified reproducible memory-safety issues in unshield's InstallShield header parsing code, reachable through the public CLI and library API when processing malformed local input files.

I would prefer not to disclose the PoC files or detailed crash information publicly before maintainers have had a chance to review them.

Is there a preferred private security contact, email address, or GitHub Security Advisory route for this project?

I can provide:

minimized PoC files
ASan logs
affected commit and release information
clean-checkout reproduction steps

Best regards,

[twogood]

Thanks! I don't need all of that, I just need a PR with a test case and a patch.

[damseleng]

Would you be willing to handle this as a security issue and request/assign a CVE or publish a security advisory for the fix? If so, I can prepare a PR with a regression test and patch.

[twogood]

Would you be willing to handle this as a security issue and request/assign a CVE or publish a security advisory for the fix? If so, I can prepare a PR with a regression test and patch.

This is a small side-project I maintain for fun, I don't have any system for handling security issues. I think that #CVE-2015-1386 was created via Debian.

[Yukimura-Aneha]

Thank you, that works for me.

I will prepare a pull request with a minimal regression test case and a patch for the InstallShield header parsing issue.

Since the project does not have a dedicated security advisory process, I will keep the PR focused on the parser robustness fix and test coverage. After the fix is accepted, I may separately request a CVE through an external CVE assignment route and will reference the final fixed commit/PR if needed.

Thanks again.