Bug 188797
| Summary: | CVE-2006-1724 Crashes with evidence of memory corruption (1.5.0.2) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Josh Bressers <bressers> |
| Component: | mozilla | Assignee: | Christopher Aillon <caillon> |
| Status: | CLOSED ERRATA | QA Contact: | Ben Levenson <benl> |
| Severity: | urgent | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | CC: | deisenst, security-response-team |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | reported=20060412,source=mozilla,embargo=yes,impact=critical | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-10-02 12:26:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Josh Bressers
2006-04-13 02:26:03 UTC
Lifting embargo *Ping* Was this bug fixed anywhere? I do not see CVE-2006-1724 listed among the items fixed in Mozilla. Is this, perhaps, a Firefox-only bug? *ping* Noticing that this bugzilla remains open. Hasn't Seamonkey already been issued to replace Mozilla for the RHEL's? If so, could this bug be closed somehow, referring folks to look at (an) RHSA for Seamonkey for the fix to this issue? As a matter of fact, wasn't this issue fixed with Mozilla-1.7.13 instead of needing Seamonkey to fix it? Or was Mozilla-1.7.13 ever issued for RHEL? Mitre's CVE-2006-1724 indicates a couple of RHSA's were issued for this issue, but they were for: * <http://rhn.redhat.com/errata/RHSA-2006-0328.html> Firefox, and * <http://rhn.redhat.com/errata/RHSA-2006-0330.html> Thunderbird, not for Mozilla/Seamonkey... Ah. Looks like this Mozilla issue is fixed by: <http://rhn.redhat.com/errata/RHSA-2006-0329.html>. Hmm, RHSA-2006:0329 doesn't list CVE-2006-1724, we'll have to look if this was deliberate or if it's a mistake. RHSA-2006:0329 not listing this CVE id is a mistake, I'm fixing it now. Thanks for catching this. |