WICG / WICG/declarative-partial-updates

Fork bombing

Open
#101 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Bikeshed
Stars
135
Forks
13
Avg merge
12m
Merged PRs (30d)
3

Description

It is possible with this proposal if you control any part of the content of the web page to output content which will DOS the system by expanding a small chunk of HTML to a very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very large chunk of DOM.

Yes I generated a lot of very's by copy pasting a few of them, because that's what a fork bomb does.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the declarative partial updates proposal and the issue's HTML/DOM expansion concern. Determine whether a small, user-controlled fragment can cause unbounded DOM growth, then define and verify a bounded behavior before considering the issue complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
security, web-dev
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.