Low: mod_auth_digest possible stack overflow by one nul byteĪpache HTTP Server versions 2.4.0 to 2.4.46 A specially crafted Digest nonce can cause a stack overflow in mod_auth_digest. Low: mod_proxy_http NULL pointer dereferenceĪpache HTTP Server versions 2.4.41 to 2.4.46 mod_proxy_http can be made to crash (NULL pointer dereference) with specially crafted requests using both Content-Length and Transfer-Encoding headers, leading to a Denial of ServiceĪcknowledgements: Reported by Marc Stern () Reported to security team Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') vulnerability in mod_proxy_ajp of Apache HTTP Server allows an attacker to smuggle requests to the AJP server it forwards requests to. Fixed in Apache HTTP Server 2.4.54 moderate: mod_proxy_ajp: Possible request smuggling Consult the Apache httpd 2.2 vulnerabilities list for more information. The initial GA release, Apache httpd 2.4.1, includes fixes for all vulnerabilities which have been resolved in Apache httpd 2.2.22 and all older releases. Please send comments or corrections for these vulnerabilities to the Security Team. Please note that if a vulnerability is shown below as being fixed in a "-dev" release then this means that a fix has been applied to the development source tree and will be part of an upcoming full release. We also list the versions the flaw is known to affect, and where a flaw has not been verified list the version with a question mark. Each vulnerability is given a security impact rating by the Apache security team - please note that this rating may well vary from platform to platform. This page lists all security vulnerabilities fixed in released versions of Apache HTTP Server 2.4. For information on H3C's security emergency response service and H3C product vulnerabilities, please visit. H3C advocates that every effort be made to safeguard the ultimate interests of product users, to abide by principles of responsible disclosure of security incidents, and to handle product security issues in accordance with security issues mechanisms. security emergency response external service Set access whitelist, only allow trusted IP to access Solr APIģ. To use identity authentication, please refer to the link for details: ģ. If the ConfigSets API is not used in the environment, you can disable the UPLOAD command, =false, refer to the link for details: Ģ. If you cannot upgrade, you can use the patch in the SOLR-14663 announcement, refer to the link: ġ. Apache Solr has officially fixed the vulnerability in the new version. Modify the parameters in the configuration file to cause remote code execution and obtain server permissions.ĪpacheSolr 6.6.0 - 6.6.5\ApacheSolr 7.0.0 - 7.7.3\ApacheSolr 8.0.0 - 8.6.2ġ. A remote attacker can use this vulnerability to combine the UPLOAD/CREATE commands to achieve unauthorized operations. If you upload configuration files through the ConfigSet API without authentication, Apache Solr will disable some dangerous functions that can be used for remote code execution by default. Recently, the Xinhua Three Offensive and Defense Laboratory monitored that Apache officially updated a notice about fixing the file upload vulnerability of Apache Solr Configset API, and carried out tracking and analysis. At present, many companies use Solr to implement their search and navigation functions. It supports REST-like API interfaces, provides distributed indexing, centralized configuration and other functions. Apache Solr is an enterprise-level search platform developed in Java and implemented based on Apache Lucene.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |