googleprojectzero / googleprojectzero/fuzzilli
Feature problem: Cyclic __proto__ value
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.3k
- Forks
- 367
- Avg merge
- 23h 53m
- Merged PRs (30d)
- 1
Description
Problem
Code generators that use setPrototype may result in a cyclic assignment of __proto__ value.
Example
const o10 = {
__proto__: 64,
};
const o11 = {
__proto__: o10,
};
o10.__proto__ = o11; //TypeError: Cyclic __proto__ value
The problem is more likely to be reproduced with the following generators weighting.
Contributor guide
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
Begin with the JavaScript example and the attached generator-weighting file; trace the setPrototype generator responsible for producing the cyclic assignment. Reproduce the TypeError, then establish the expected generator behavior and a regression check for the reported case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, swift
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100