Security: preferred channel to report a vulnerability privately?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 115
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Hi — I'm a security researcher and I've identified what I believe is a security issue in certvalidator (a denial-of-service condition reachable through normal certificate-path validation). I'd like to disclose it responsibly and privately, with a proof of concept and a suggested fix.
I'm not including any technical detail here to avoid publicly disclosing an unpatched issue.
This repository currently has no SECURITY.md and GitHub Private Vulnerability Reporting appears to be disabled (Security → Advisories → "Report a vulnerability" is not available). Could you either:
- Enable Private Vulnerability Reporting for this repo (Settings → Code security → "Private vulnerability reporting"), so I can file a private advisory here; or
- Share a security contact / email I can send the report to?
Happy to provide the full write-up and PoC as soon as there's a private channel. Thanks!
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.
Research direction
Review the repository's Settings → Code security options and check whether SECURITY.md exists, as requested in the issue. The work is done when a private reporting channel is enabled or a security contact and disclosure instructions are documented for the researcher.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100