Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Rohkem teavet

When will CVE-2019-11754 will be patched on ESR 68 ?

  • 3 vastust
  • 1 on selline probleem
  • 17 views
  • Viimati vastas philipp

more options

Dear All From what I see this Vulnerability , is only patched in 69.0.1 https://www.mozilla.org/en-US/security/advisories/mfsa2019-31/ But there have been later ESR 68.2.0 patched released that does not have this mitigated . Will 68 channel ever will get this patched , or will we need to wait for ESR 69 ? When is that supposed to be released ?

Dear All From what I see this Vulnerability , is only patched in 69.0.1 https://www.mozilla.org/en-US/security/advisories/mfsa2019-31/ But there have been later ESR 68.2.0 patched released that does not have this mitigated . Will 68 channel ever will get this patched , or will we need to wait for ESR 69 ? When is that supposed to be released ?

Valitud lahendus

the bug referenced in https://www.mozilla.org/en-US/security/advisories/mfsa2019-31/ hasn't been made public yet unfortunately, so you won't be able to confirm this by yourself yet :-/

the underlying cause was just introduced in Firefox 69 though, so 69.0 is the only version affected by this vulnerability.

Loe vastust kontekstis 👍 1

All Replies (3)

more options

hello, firefox 68esr is not affected by CVE-2019-11754.

more options

Thanks

From this source where many security tools gather their information for baseline scans (e.g. Qualys and such) it says that this is affected FF under 69.0.1 and does not mention ESR the same as CVE-2019-11753 for example: https://www.cvedetails.com/vulnerability-list/vendor_id-452/product_id-3264/Mozilla-Firefox.html

is there any place on line that confirm that this vuln does not affect ESR 68 ?

more options

Valitud lahendus

the bug referenced in https://www.mozilla.org/en-US/security/advisories/mfsa2019-31/ hasn't been made public yet unfortunately, so you won't be able to confirm this by yourself yet :-/

the underlying cause was just introduced in Firefox 69 though, so 69.0 is the only version affected by this vulnerability.