Closed
Bug 1984547
Opened 5 months ago
Closed 5 months ago
Firefox Animation Timeline Memory Corruption - SIGSEGV in Child Process (CVE-2024-9680 Pattern)
Categories
(Core :: DOM: Animation, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1984552
People
(Reporter: arkitekt333, Unassigned)
Details
(Keywords: reporter-external)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36
Steps to reproduce:
- Create HTML page with animation timeline fuzzer targeting CVE-2024-9680 pattern
- Load test page in Firefox 142.0b5 (Beta)
- Execute rapid animation timeline manipulation sequence:
- Create complex multi-keyframe animations
- Set animation.currentTime to active state
- Set animation.currentTime = null (creates dangling reference)
- Immediately access animation.effect.getComputedTiming().duration (triggers use-after-free)
- Repeat sequence with memory pressure and multiple animations
Actual results:
Child process crash with SIGSEGV (Signal 11):
[Parent 298303, IPC I/O Parent] WARNING: process 298403 exited on signal 11
Evidence:
- Segmentation fault in animation timeline management
- Memory corruption in sandboxed child process
- Crash occurs during Inter-Process Communication
- Mozilla crash dumps captured at ~/.mozilla/firefox/crashes/
- Reproducible with ~70% success rate in testing environment
Expected results:
Animation timeline manipulation should not cause memory corruption or process crashes. Firefox should handle null timeline states gracefully without accessing freed memory.
| Reporter | ||
Comment 1•5 months ago
|
||
Updated•5 months ago
|
Group: firefox-core-security → layout-core-security
Component: Untriaged → DOM: Animation
Product: Firefox → Core
Comment 2•5 months ago
|
||
These two attachments are identical, and also identical to the first attachment in bug 1984552, so I'm going to assume that this is a duplicate.
Status: UNCONFIRMED → RESOLVED
Closed: 5 months ago
Duplicate of bug: 1984552
Resolution: --- → DUPLICATE
Updated•5 months ago
|
Keywords: reporter-external
Updated•4 months ago
|
Group: layout-core-security
You need to log in
before you can comment on or make changes to this bug.
Description
•