CVE-2006-5159
What it is
Stack-based buffer overflow in Mozilla Firefox allows remote attackers to execute arbitrary code via unspecified vectors involving JavaScript. NOTE: the vendor and original researchers have released a follow-up comment disputing the severity of this issue, in which the researcher states that "we mentioned that there was a previously known Firefox vulnerability that could result in a stack overflow ending up in remote code execution. However, the code we presented did not in fact do this... I have not succeeded in making this code do anything more than cause a crash and eat up system resources"
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 6.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 6.3% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 6.3% · EPSS, next 30 days
- Record status
- Modified
Affected
- Mozilla Firefox 0.8
- Mozilla Firefox 0.9
- Mozilla Firefox 0.9.1
- Mozilla Firefox 0.9.2
- Mozilla Firefox 0.9.3
- Mozilla Firefox 0.10
- Mozilla Firefox 0.10.1
- Mozilla Firefox 1.0
Attack profile CVSS 2.0 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
Raw vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2006-5159.md and follow it. Check whether this project is affected by CVE-2006-5159. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- http://developer.mozilla.org/devnews/index.php/2006/10/02/update-possible-vulnerability-reported-at-toorcon/
- http://securityreason.com/securityalert/1678
- http://securitytracker.com/id?1016962
- http://www.securityfocus.com/archive/1/447493/100/0/threaded
- http://www.securityfocus.com/archive/1/447497/100/0/threaded
- http://www.securityfocus.com/bid/20282
- http://www.securityfocus.com/bid/20294
- http://www.securitypronews.com/insiderreports/insider/spn-49-20061003FirefoxVulnerabilityClaimWasAJoke.html
- https://exchange.xforce.ibmcloud.com/vulnerabilities/29317
- http://developer.mozilla.org/devnews/index.php/2006/10/02/update-possible-vulnerability-reported-at-toorcon/
- http://securityreason.com/securityalert/1678
- http://securitytracker.com/id?1016962
- http://www.securityfocus.com/archive/1/447493/100/0/threaded
- http://www.securityfocus.com/archive/1/447497/100/0/threaded
- http://www.securityfocus.com/bid/20282
- http://www.securityfocus.com/bid/20294
- http://www.securitypronews.com/insiderreports/insider/spn-49-20061003FirefoxVulnerabilityClaimWasAJoke.html
- https://exchange.xforce.ibmcloud.com/vulnerabilities/29317