# Apache server upgradation- 139574 - Apache 2.4.x \< 2.4.46 Multiple Vulnerabilities

**URL:** <https://forums.suse.com/t/apache-server-upgradation-139574-apache-2-4-x-2-4-46-multiple-vulnerabilities/35525>\
**Category:** SLES SAP Applications\
**Created:** [March 23, 2021, 11:08am UTC](https://forums.suse.com/t/apache-server-upgradation-139574-apache-2-4-x-2-4-46-multiple-vulnerabilities/35525 "2021-03-23T11:08:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MRPL](https://avatars.discourse-cdn.com/v4/letter/m/5f9b8f/32.png) [@MRPL](https://forums.suse.com/u/MRPL)\
**Post date:** [March 23, 2021, 11:08am UTC](https://forums.suse.com/t/apache-server-upgradation-139574-apache-2-4-x-2-4-46-multiple-vulnerabilities/35525/1 "2021-03-23T11:08:17Z")

</div>

Team,  
We are supposed to upgrade Apache as per Multiple Vulnerabilities.  
Therefore,. please suggest us to fix the same with downloading link for the apache RPM.  
Synopsis  
The remote web server is affected by multiple vulnerabilities.  
Description  
The version of Apache httpd installed on the remote host is prior to 2.4.46. It is, therefore, affected by multiple vulnerabilities as referenced in the 2.4.46 advisory.

- Apache HTTP server 2.4.32 to 2.4.44 mod\_proxy\_uwsgi info disclosure and possible RCE (CVE-2020-11984)
- Apache HTTP Server versions 2.4.20 to 2.4.43 When trace/debug was enabled for the HTTP/2 module and on certain traffic edge patterns, logging statements were made on the wrong connection, causing concurrent use of memory pools. Configuring the LogLevel of mod\_http2 above info will mitigate this vulnerability for unpatched servers. (CVE-2020-11993)
- Apache HTTP Server versions 2.4.20 to 2.4.43. A specially crafted value for the ‘Cache-Digest’ header in a HTTP/2 request would result in a crash when the server actually tries to HTTP/2 PUSH a resource afterwards.  
Configuring the HTTP/2 feature via H2Push off will mitigate this vulnerability for unpatched servers.  
(CVE-2020-9490)  
Note that Nessus has not tested for this issue but has instead relied only on the application’s self-reported version number.  
Solution  
Upgrade to Apache version 2.4.46 or later.  
Risk Factor  
High

Thanks,  
Harish T

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [March 23, 2021, 12:25pm UTC](https://forums.suse.com/t/apache-server-upgradation-139574-apache-2-4-x-2-4-46-multiple-vulnerabilities/35525/2 "2021-03-23T12:25:03Z")

</div>

@MRPL Hi and welcome to the Forum 🙂  
Another user just had a similar same question, see [https://forums.suse.com/discussion/15308/minor-question-but-strange-security-update-for-php-7-4-on-sles-15-sp2](https://forums.suse.com/discussion/15308/minor-question-but-strange-security-update-for-php-7-4-on-sles-15-sp2)  
The issue is scanners that check only version numbers…

---

<div class="post-metadata">

**Author:** ![MRPL](https://avatars.discourse-cdn.com/v4/letter/m/5f9b8f/32.png) [@MRPL](https://forums.suse.com/u/MRPL)\
**Post date:** [March 24, 2021, 9:57am UTC](https://forums.suse.com/t/apache-server-upgradation-139574-apache-2-4-x-2-4-46-multiple-vulnerabilities/35525/3 "2021-03-24T09:57:45Z")

</div>

Thanks @malcolmlewis  
But that answer will not match for my question.
