9.3
CVE-2009-1837
- EPSS 2.18%
- Published 12.06.2009 21:30:00
- Last modified 09.04.2025 00:30:58
- Source secalert@redhat.com
- Teams watchlist Login
- Open Login
Race condition in the NPObjWrapper_NewResolve function in modules/plugin/base/src/nsJSNPRuntime.cpp in xul.dll in Mozilla Firefox 3 before 3.0.11 might allow remote attackers to execute arbitrary code via a page transition during Java applet loading, related to a use-after-free vulnerability for memory associated with a destroyed Java object.
Data is provided by the National Vulnerability Database (NVD)
Debian ≫ Debian Linux Version5.0
Fedoraproject ≫ Fedora Version9
Fedoraproject ≫ Fedora Version10
Redhat ≫ Enterprise Linux Version4.0
Redhat ≫ Enterprise Linux Version5.0
Redhat ≫ Enterprise Linux Desktop Version4.0
Redhat ≫ Enterprise Linux Desktop Version5.0
Redhat ≫ Enterprise Linux Eus Version4.8
Redhat ≫ Enterprise Linux Eus Version5.3
Redhat ≫ Enterprise Linux Server Version4.0
Redhat ≫ Enterprise Linux Server Version5.0
Redhat ≫ Enterprise Linux Server Aus Version5.3
Redhat ≫ Enterprise Linux Workstation Version4.0
Redhat ≫ Enterprise Linux Workstation Version5.0
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
| Type | Source | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 2.18% | 0.828 |
| Source | Base Score | Exploit Score | Impact Score | Vector string |
|---|---|---|---|---|
| nvd@nist.gov | 7.5 | 1.6 | 5.9 |
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
|
| nvd@nist.gov | 9.3 | 8.6 | 10 |
AV:N/AC:M/Au:N/C:C/I:C/A:C
|
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.