Red Hat Security Advisory: apache, openssl, php, tomcat security update for Stronghold
Updated versions of Stronghold 4 cross-platform are available to fix a number of vulnerabilities in OpenSSL, Apache, PHP, and Tomcat. Also included in this update are bug fixes for mod_proxy and the mod_authz_ldap package.
describes (4)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2003-0020US | medium5.0 | — | ||
Apache does not filter terminal escape sequences from its error logs, which could make it easier for attackers to insert those sequences into terminal emulators containing vulnerab… | ||||
| CVE-2003-0078US | medium5.0 | Exploit | ||
ssl3_get_record in s3_pkt.c for OpenSSL before 0.9.7a and 0.9.6 before 0.9.6i does not perform a MAC computation if an incorrect block cipher padding is used, which causes an infor… | ||||
| CVE-2002-1394US | high7.5 | — | ||
Apache Tomcat 4.0.5 and earlier, when using both the invoker servlet and the default servlet, allows remote attackers to read source code for server files or bypass certain protect… | ||||
| CVE-2002-1376US | high7.5 | — | ||
libmysqlclient client library in MySQL 3.x to 3.23.54, and 4.x to 4.0.6, does not properly verify length fields for certain responses in the (1) read_rows or (2) read_one_row routi… | ||||
references
External citations — patches, advisories, analysis.
remediations (4)
- FixedRed Hat Stronghold 4
Fixed Stronghold 4 packages are now available via the update agent service; run $ bin/agent from the Stronghold 4 install root to upgrade an existing Stronghold 4 installation to the new package versions. After upgrading Stronghold, the server must be completely restarted by running the following commands from the install root: $ bin/stop-server $ bin/stop-tomcat $ bin/start-tomcat $ bin/start-server For more information on how to upgrade between releases of Stronghold 4, see http://stronghold.redhat.com/support/upgrade-sh4
https://access.redhat.com/errata/RHSA-2003:082 - FixedRed Hat Stronghold 4
Fixed Stronghold 4 packages are now available via the update agent service; run $ bin/agent from the Stronghold 4 install root to upgrade an existing Stronghold 4 installation to the new package versions. After upgrading Stronghold, the server must be completely restarted by running the following commands from the install root: $ bin/stop-server $ bin/stop-tomcat $ bin/start-tomcat $ bin/start-server For more information on how to upgrade between releases of Stronghold 4, see http://stronghold.redhat.com/support/upgrade-sh4
https://access.redhat.com/errata/RHSA-2003:082 - FixedRed Hat Stronghold 4
Fixed Stronghold 4 packages are now available via the update agent service; run $ bin/agent from the Stronghold 4 install root to upgrade an existing Stronghold 4 installation to the new package versions. After upgrading Stronghold, the server must be completely restarted by running the following commands from the install root: $ bin/stop-server $ bin/stop-tomcat $ bin/start-tomcat $ bin/start-server For more information on how to upgrade between releases of Stronghold 4, see http://stronghold.redhat.com/support/upgrade-sh4
https://access.redhat.com/errata/RHSA-2003:082 - FixedRed Hat Stronghold 4
Fixed Stronghold 4 packages are now available via the update agent service; run $ bin/agent from the Stronghold 4 install root to upgrade an existing Stronghold 4 installation to the new package versions. After upgrading Stronghold, the server must be completely restarted by running the following commands from the install root: $ bin/stop-server $ bin/stop-tomcat $ bin/start-tomcat $ bin/start-server For more information on how to upgrade between releases of Stronghold 4, see http://stronghold.redhat.com/support/upgrade-sh4
https://access.redhat.com/errata/RHSA-2003:082
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan