Closed Bug 1896954 Opened 1 year ago Closed 10 months ago

Fuzzing for Wasm JS Promise Integration.

Categories

(Core :: Fuzzing, task)

Product:
Core
Component:
Fuzzing
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
139 Branch
Tracking Flags:
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox137 --- unaffected
firefox138 --- unaffected
firefox139 --- fixed

People

(Reporter: yury, Assigned: yury, NeedInfo)

References

(Blocks 1 open bug)

Details

(Keywords: sec-other)

Attachments

(1 file)

Bug 1896954 - Enable fuzzing for JSPI. r?rhunt
48 bytes, text/x-phabricator-request
Details | Review

Hi,

I would like to request fuzzing for Wasm JS Promise Integration.

Meta bug: Bug 1850627
Preferences: javascript.options.wasm_js_promise_integration / --setpref=wasm_js_promise_integration
Platforms: x64/aarch64 (x86 after bug 1896218)
Existing tests: js/src/jit-test/tests/wasm/js-promise-integration/
Testing may start as of:
Targeted Release Version: n/a

Blocks: wasm-jspi-proto
Group: core-security → javascript-core-security
Keywords: sec-other
Blocks: wasm-jspi
No longer blocks: wasm-jspi-proto

Updated https://github.com/MozillaSecurity/fuzzing-shells-private/ to update wasm-call.js fuzzing of valid calls between JS/Wasm with JSPI API. See https://github.com/MozillaSecurity/fuzzing-shells-private/pull/11

Assignee: nobody → ydelendik
Status: NEW → ASSIGNED

The wasm fuzzing flag was changed to true

Flags: needinfo?(choller)

https://hg.mozilla.org/mozilla-central/rev/8d12a5db9858

Group: javascript-core-security → core-security-release
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
status-firefox139: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 139 Branch
QA Whiteboard: [sec] [qa-triage-done-c140/b139]
Flags: qe-verify-
Group: core-security-release
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: