Skip to content

Add guidelines for contacting the security WG to avoid spam etc #796

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 16, 2025
Merged

Add guidelines for contacting the security WG to avoid spam etc #796

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
56e7b43
suggestion to avoid spam on security ml
Carreau Apr 28, 2025
6d3d348
Update security.md
Carreau Apr 28, 2025
b648f89
Cleaning up language
choldgraf Apr 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions security.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,39 @@ you can either:
- report it to [security@ipython.org](mailto:security@ipython.org) if opening a GHSA is not possible, or you are unsure
where it will belong.


We do not currently run bug bounty programs, and do not currently reward
vulnerability discovery.

If you prefer to encrypt your security reports,
you can use [this PGP public key](assets/ipython_security.asc).


### Reports to avoid

If you are unsure it is always best to contact us, though as an open source
project maintained on volunteer time, we only have limited resources to spare,
so please be mindful of our time.

- Avoid sending bare report of website scanning tools without some limited
understanding saying you found a vulnerability:

- Example: we receive regular report of js vulnerability or wrong CORS on
static websites, mostly jupyter.org and other documentation on
`*.readthedocs.io`. As static website those are not affected.
- Better:
- You ran a tool and think there is vulnerability because you are
learning, include you uncertainty in the object/body of the message.
- You are a security researcher: Verify the tool claim and try to develop
Copy link
Preview

Copilot AI Apr 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo in the phrase 'include you uncertainty'; consider replacing it with 'include your uncertainty'.

Suggested change
learning, include you uncertainty in the object/body of the message.
- You are a security researcher: Verify the tool claim and try to develop
learning, include your uncertainty in the object/body of the message.

Copilot uses AI. Check for mistakes.

a POC of exploiting the vulnerability/fixing it.

- Avoid sending mass email to security@ipython.org,
(especially with dozen of other emails from bug bounty program in CC)

- Avoid asking us if we run a bug bounty program on private channel, or reward
discovery, discuss it on the public forum.


## Vulnerability information

Known vulnerabilities are tracked using the [CVE vendor ID 15653 for Jupyter](https://www.cvedetails.com/vulnerability-list/vendor_id-15653/Jupyter.html).
Expand Down
Loading