We are installing 24.1.1 image on AWS ECR and the Scan is showing a lot of vulnerabilities for search. Are these known and are there fixes for them? see below
search-24.1.1
Name |
Vulnerable package |
Severity |
Description |
Status |
Fixed in |
Exploit available |
Fix available |
|---|---|---|---|---|---|---|---|
CVE-2021-44228 |
org.apache.logging.log4j:log4j-core |
CRITICAL |
Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects. |
ACTIVE |
2.15.0 |
YES |
YES |
CVE-2022-1471 |
org.yaml:snakeyaml |
CRITICAL |
SnakeYaml’s Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml’s SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend upgrading to version 2.0 and beyond. |
ACTIVE |
2 |
NO |
YES |
CVE-2017-12629 |
org.apache.lucene:lucene-queryparser |
CRITICAL |
Remote code execution occurs in Apache Solr before 7.1 with Apache Lucene before 7.1 by exploiting XXE in conjunction with use of a Config API add-listener command to reach the RunExecutableListener class. Elasticsearch, although it uses Lucene, is NOT vulnerable to this. Note that the XML external entity expansion vulnerability occurs in the XML Query Parser which is available, by default, for any query request with parameters deftype=xmlparser and can be exploited to upload malicious data to the /upload request handler or as Blind XXE using ftp wrapper in order to read arbitrary local files from the Solr server. Note also that the second vulnerability relates to remote code execution using the RunExecutableListener available on all affected versions of Solr. |
ACTIVE |
7.1.0 |
YES |
YES |
CVE-2021-45046 |
org.apache.logging.log4j:log4j-core |
CRITICAL |
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default. |
ACTIVE |
2.16.0 |
YES |
YES |
CVE-2019-20445 |
io.netty:netty-handler, io.netty:netty, io.netty:netty-codec-http |
CRITICAL |
HttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length header to be accompanied by a second Content-Length header, or by a Transfer-Encoding header. |
ACTIVE |
4.1.45 |
NO |
PARTIAL |
CVE-2016-6814 |
org.codehaus.groovy:groovy |
CRITICAL |
When an application with unsupported Codehaus versions of Groovy from 1.7.0 to 2.4.3, Apache Groovy 2.4.4 to 2.4.7 on classpath uses standard Java serialization mechanisms, e.g. to communicate between servers or to store local data, it was possible for an attacker to bake a special serialized object that will execute code directly when deserialized. All applications which rely on serialization and do not isolate the code which deserializes objects were subject to this vulnerability. |
ACTIVE |
2.4.8 |
NO |
YES |
CVE-2024-37371 |
libkrb5support0, libgssapi-krb5-2, libk5crypto3, libkrb5-3 |
CRITICAL |
In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields. |
ACTIVE |
0:1.17-6ubuntu4.6 |
NO |
YES |
CVE-2024-45491 |
expat, libexpat1 |
CRITICAL |
An issue was discovered in libexpat before 2.6.3. dtdCopy in xmlparse.c can have an integer overflow for nDefaultAtts on 32-bit platforms (where UINT_MAX equals SIZE_MAX). |
ACTIVE |
0:2.2.9-1ubuntu0.7 |
NO |
YES |
CVE-2024-45492 |
expat, libexpat1 |
CRITICAL |
An issue was discovered in libexpat before 2.6.3. nextScaffoldPart in xmlparse.c can have an integer overflow for m_groupSize on 32-bit platforms (where UINT_MAX equals SIZE_MAX). |
ACTIVE |
0:2.2.9-1ubuntu0.7 |
NO |
YES |
CVE-2019-20444 |
io.netty:netty, io.netty:netty-codec-http |
CRITICAL |
HttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with an incorrect syntax, or might be interpreted as an “invalid fold.” |
ACTIVE |
NotAvailable |
NO |
PARTIAL |