CVE-2021-45046 caused by CVE-2021-44228 for log4j

[Brian_Keller]

CVE-2021-45046 was released Dec 14 regarding a denial of service vulnerability introduced in log4j 2.15.0. Is Hyland aware of this new vulnerability and, if so, what is the impact? log4j version 2.16.0 was put out to remediate this new issue. Also, the recommended actions for CVE-2021-44228 does not fix this new vulnerability.

Edited to add the link to CVE-2021-45046:
NVD - CVE-2021-45046 (nist.gov)

[Julianne_Horner]

Hyland's post about this issue: CVE-2021-44228 related to Apache Log4j Security Advisory (hyland.com)

[Ryan_Wakefield]

@Julianne Horner , unfortunately that link is only for the CVE-2021-44228 vulnerability. Brian is asking about that CVE-2021-45046 vulnerability that came out as a result of them releasing the 2.15.0 version (which is supposedly fixed by upgrading to the 2.16.0 version of Log4j).

[Brian_Keller]

Julianne, Ryan is correct below. I am asking about the follow-up issue introduced because of CVE-2021-44228, not about that CVE itself.