- which has log4j 2.17.0 and it’s shows it’s vulnerable to CVE-2021-44832 in below link
- Can you please check if it’s vulnerable and how can we mitigate it.
Without any official statement from SonarSource, you might comforted by this message from a fellow community user.
Hi, Thanks for the reply.
But it doesn’t provide any new information where it says it’s not vulnerable to the threat.
Can we have more info on the same or when the patch or updated versions would be coming.
Welcome to the community!
As previously stated, our security researchers have found no way to exploit even the original vulnerability in SonarQube. The patches we released were issued “from an abundance of caution” and “to eliminate confusion and avoid false-positive[s] from vulnerability scanning tools”.
The CVE you reference requires “a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server”. Since SonarQube’s only use of Log4J is via Elasticsearch, I think you can rest easy that those conditions don’t exist.
In short, we do not plan to release patches to address this CVE.