googleprojectzero / googleprojectzero/fuzzilli

Feature problem: Top-level prototype assignment

Open
#451 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
2.3k
Forks
367
Avg merge
23h 53m
Merged PRs (30d)
1

Description

Problem

A code generator using setPrototype may generate code that assigns a value to the top-level prototype.

Example

const v11 = { a: 1 };
const v20 = v11.__proto__;
const newProto = { b: 2 };
v20.__proto__ = newProto; //TypeError: Immutable prototype object 'Object.prototype' cannot have their prototype set

The problem is more likely to be reproduced with the following generators weighting.

top-level proto.txt

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

No source file or test is named. Start by locating the generator path that implements setPrototype, then reproduce the issue using the attached top-level proto.txt weighting and the JavaScript example. Done means the top-level prototype case has defined handling and the reproduced failure is covered by project tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, swift
Domain
testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.