CVE-2006-4801 roxio toast: Race Condition
roxio toast: no CVSS score yet. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
Race condition in Deja Vu, as used in Roxio Toast Titanium 7 and possibly other products, allows local users to execute arbitrary code via temporary files, including dejavu_manual.rb, which are executed with raised privileges.
- EPSS
- 0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
- OWASP Top 10
- A06:2025 Insecure Design
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Vendor advisory: http://secunia.com/advisories/21867
- Vendor advisory: http://www.netragard.com/pdfs/research/ROXIO_RACE_NETRAGARD-20060624.txt
Ask an AI about this CVE
Show the prompt
Explain CVE-2006-4801 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2006-4801?via=ask-ai-copy and https://cve.bz/cve/CVE-2006-4801?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2006-4801 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| roxio:toast | 7 |
Attack patterns (CAPEC)
- CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
- CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.