-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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.
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
[hackerone] IPFS crash #24093
Labels
bug
feature/web3/ipfs
OS/Desktop
priority/P2
A bad problem. We might uplift this to the next planned release.
QA Pass-macOS
QA/Yes
release-notes/exclude
security
Milestone
Comments
cypt4
added
priority/P2
A bad problem. We might uplift this to the next planned release.
feature/web3/ipfs
labels
Jul 18, 2022
cypt4
added a commit
to brave/brave-core
that referenced
this issue
Jul 18, 2022
Fixes brave/brave-browser#24093 Don't allow to commit raw ipfs\ipns navigations.
25 tasks
stephendonner
added
QA/In-Progress
Indicates that QA is currently in progress for that particular issue
bug
labels
Aug 4, 2022
Verification
|
Brave | 1.43.56 Chromium: 104.0.5112.81 (Official Build) dev (x86_64) |
---|---|
Revision | 5b7b76419d50f583022568b6764b630f6ddc9208-refs/branch-heads/5112@{#1309} |
OS | macOS Version 13.0 (Build 22A5311f) |
Test Setup
Created webserver instance via python3 -m http.server 8080
, from /Desktop/issue24093
.
For the "incorrect {ipfs
, ipns
} tests", I ensured the following HTML snippets (from HackerOne and @cypt4) don't crash on load:
ipfs-crash-test-1.html
(dotted-quad IP address)ipfs-crash-test-2.html
(emptyipfs://
scheme)ipfs-crash-test-3.html
(full IPFS URL)ipfs-crash-test-4.html
(redirect testcase)ipfs-crash-test-5.html
(emptyipns://
scheme)ipfs-crash-test-6.html
(full IPNS URL)
*Encountered the following crash while testing:
IPFS disabled - PASSED*
:
Steps:
- install
1.43.59
- launch Brave
- [open a new Private window, if specified]
- open the appropriate local HTML testcase(s)
- Check iframe with correct ipfs url in normal tab
- Check iframe with correct ipfs url in private tab
- Check iframe with incorrect ipfs url in normal tab
- Check iframe with incorrect ipfs url in private tab
- Check iframe with correct ipns url in normal tab
- Check iframe with correct ipns url in private tab
- Check iframe with incorrect ipns url in normal tab
- Check iframe with incorrect ipns url in private tab
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
---|---|---|---|---|---|---|---|
issue 24211 | issue 24211 | issue 24211 | issue 24211 |
IPFS enabled, local node - PASSED*
:
Steps:
- install
1.43.59
- launch Brave
- load
ipns://ipfs.io
- click on
Use a Brave local IPFS node
- [open a new Private window, if specified]
- open the appropriate local HTML testcase(s)
- Check iframe with correct ipfs url in normal tab
- Check iframe with correct ipfs url in private tab
- Check iframe with incorrect ipfs url in normal tab
- Check iframe with incorrect ipfs url in private tab
- Check iframe with correct ipns url in normal tab
- Check iframe with correct ipns url in private tab
- Check iframe with incorrect ipns url in normal tab
- Check iframe with incorrect ipns url in private tab
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
---|---|---|---|---|---|---|---|
issue 24211 | issue 24211 | issue 24211 | issue 24211 |
IPFS enabled, gateway - PASSED*
:
Steps:
- install
1.43.59
- launch Brave
- load
ipns://ipfs.io
- click on
Use a public gateway
- opened
brave://settings/ipfs
and setIPFS public gateway address
tohttps://cf-ipfs.com
(it's faster, IMHO) - [open a new Private window, if specified]
- open the appropriate local HTML testcase(s)
- Check iframe with correct ipfs url normal tab
- Check iframe with correct ipfs url private tab
- Check iframe with incorrect ipfs url in normal tab
- Check iframe with incorrect ipfs url in private tab
- Check iframe with correct ipns url in normal tab
- Check iframe with correct ipns url in private tab
- Check iframe with incorrect ipns url in normal tab
- Check iframe with incorrect ipns url in private tab
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
---|---|---|---|---|---|---|---|
issue 24211 | issue 24211 | issue 24211 | issue 24211 |
25 tasks
stephendonner
added
QA Pass-macOS
and removed
QA/In-Progress
Indicates that QA is currently in progress for that particular issue
labels
Aug 5, 2022
I passed this, but we need to uplift #24211; left a comment in brave/brave-core#14313 (comment) to that effect. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
feature/web3/ipfs
OS/Desktop
priority/P2
A bad problem. We might uplift this to the next planned release.
QA Pass-macOS
QA/Yes
release-notes/exclude
security
see https://hackerone.com/reports/1636430 for details
credit: neeythann
The text was updated successfully, but these errors were encountered: