9 matches found
CVE-2023-4578 Error reporting methods in SpiderMonkey could have triggered an Out of Memory Exception
When calling JS::CheckRegExpSyntax a Syntax Error could have been set which would end in calling convertToRuntimeErrorAndClear. A path in the function could attempt to allocate memory when none is available which would have caused a newly created Out of Memory exception to be mishandled as a Synt...
CVE-2023-4578
When calling JS::CheckRegExpSyntax a Syntax Error could have been set which would end in calling convertToRuntimeErrorAndClear. A path in the function could attempt to allocate memory when none is available which would have caused a newly created Out of Memory exception to be mishandled as a Synt...
CVE-2023-4578
When calling "JS::CheckRegExpSyntax" a Syntax Error could have been set which would end in calling "convertToRuntimeErrorAndClear". A path in the function could attempt to allocate memory when none is available which would have caused a newly created Out of Memory exception to be mishandled as a...
CVE-2023-4578: Allocation of Resources Without Limits or Throttling
When calling JS::CheckRegExpSyntax a Syntax Error could have been set which would end in calling convertToRuntimeErrorAndClear. A path in the function could attempt to allocate memory when none is available which would have caused a newly created Out of Memory exception to be mishandled as a Synt...
Mozilla: Error reporting methods in SpiderMonkey could have triggered an Out of Memory Exception
The Mozilla Foundation Security Advisory describes this flaw as: When calling JS::CheckRegExpSyntax a Syntax Error could have been set which would end in calling convertToRuntimeErrorAndClear. A path in the function could attempt to allocate memory when none is available which would have caused a...
Mozilla: Error reporting methods in SpiderMonkey could have triggered an Out of Memory Exception
The Mozilla Foundation Security Advisory describes this flaw as: When calling JS::CheckRegExpSyntax a Syntax Error could have been set which would end in calling convertToRuntimeErrorAndClear. A path in the function could attempt to allocate memory when none is available which would have caused a...
Mozilla: Error reporting methods in SpiderMonkey could have triggered an Out of Memory Exception
The Mozilla Foundation Security Advisory describes this flaw as: When calling JS::CheckRegExpSyntax a Syntax Error could have been set which would end in calling convertToRuntimeErrorAndClear. A path in the function could attempt to allocate memory when none is available which would have caused a...
CVE-2023-4578
When calling JS::CheckRegExpSyntax a Syntax Error could have been set which would end in calling convertToRuntimeErrorAndClear. A path in the function could attempt to allocate memory when none is available which would have caused a newly created Out of Memory exception to be mishandled as a Synt...
PT-2023-4745
Name of the Vulnerable Software and Affected Versions Firefox versions prior to 117 Firefox ESR versions prior to 115.2 Thunderbird versions prior to 115.2 Description The issue is related to the JavaScript engine SpiderMonkey in Mozilla Firefox, Firefox ESR, and Thunderbird. It involves a...