CVE-2003-0020
mediumpriority · track · 26EPSS 0.165 · 97 %ileEUUSEPSS · scored 2026-10-26
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 vulnerabilities related to escape sequences.
remediations
Vendor fix, mitigation, or workaround guidance, as published by each source.
A vendor fix is available.
- FixedRed Hat Stronghold 4redhat_csaf
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 - FixedStronghold 4 for Red Hat Enterprise Linuxredhat_csaf
Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system.
https://access.redhat.com/errata/RHSA-2003:083 - FixedRed Hat Stronghold 3redhat_csaf
We have backported the security fixes for the versions of OpenSSL, Apache and PHP included in Stronghold 3. Stronghold 3.0 build code 3021 is now available which includes these fixes, and can be downloaded from http://stronghold.redhat.com/sh3/ For information on how to upgrade between releases of Stronghold 3.0, see http://stronghold.redhat.com/support/upgrade-sh3.xml
https://access.redhat.com/errata/RHSA-2003:104 - FixedRed Hat Linux 8.0redhat_csaf
Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system.
https://access.redhat.com/errata/RHSA-2003:139 - FixedRed Hat Linux 9redhat_csaf
Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system.
https://access.redhat.com/errata/RHSA-2003:139 - FixedRed Hat Linux 7.1redhat_csaf
Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. If up2date fails to connect to Red Hat Network due to SSL Certificate Errors, you need to install a version of the up2date client with an updated certificate. The latest version of up2date is available from the Red Hat FTP site and may also be downloaded directly from the RHN website: https://rhn.redhat.com/help/latest-up2date.pxt
https://access.redhat.com/errata/RHSA-2003:243 - FixedRed Hat Linux 7.2redhat_csaf
Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. If up2date fails to connect to Red Hat Network due to SSL Certificate Errors, you need to install a version of the up2date client with an updated certificate. The latest version of up2date is available from the Red Hat FTP site and may also be downloaded directly from the RHN website: https://rhn.redhat.com/help/latest-up2date.pxt
https://access.redhat.com/errata/RHSA-2003:243 - FixedRed Hat Linux 7.3redhat_csaf
Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. If up2date fails to connect to Red Hat Network due to SSL Certificate Errors, you need to install a version of the up2date client with an updated certificate. The latest version of up2date is available from the Red Hat FTP site and may also be downloaded directly from the RHN website: https://rhn.redhat.com/help/latest-up2date.pxt
https://access.redhat.com/errata/RHSA-2003:243 - FixedRed Hat Enterprise Linux AS (Advanced Server) version 2.1 redhat_csaf
Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. If up2date fails to connect to Red Hat Network due to SSL Certificate Errors, you need to install a version of the up2date client with an updated certificate. The latest version of up2date is available from the Red Hat FTP site and may also be downloaded directly from the RHN website: https://rhn.redhat.com/help/latest-up2date.pxt
https://access.redhat.com/errata/RHSA-2003:244 - FixedRed Hat Enterprise Linux ES version 2.1redhat_csaf
Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. If up2date fails to connect to Red Hat Network due to SSL Certificate Errors, you need to install a version of the up2date client with an updated certificate. The latest version of up2date is available from the Red Hat FTP site and may also be downloaded directly from the RHN website: https://rhn.redhat.com/help/latest-up2date.pxt
https://access.redhat.com/errata/RHSA-2003:244 - FixedRed Hat Enterprise Linux WS version 2.1redhat_csaf
Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. If up2date fails to connect to Red Hat Network due to SSL Certificate Errors, you need to install a version of the up2date client with an updated certificate. The latest version of up2date is available from the Red Hat FTP site and may also be downloaded directly from the RHN website: https://rhn.redhat.com/help/latest-up2date.pxt
https://access.redhat.com/errata/RHSA-2003:244 - FixedRed Hat Linux Advanced Workstation 2.1redhat_csaf
Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. If up2date fails to connect to Red Hat Network due to SSL Certificate Errors, you need to install a version of the up2date client with an updated certificate. The latest version of up2date is available from the Red Hat FTP site and may also be downloaded directly from the RHN website: https://rhn.redhat.com/help/latest-up2date.pxt
https://access.redhat.com/errata/RHSA-2003:244
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (15)
Products and version ranges known to be affected.
- Red Hat Enterprise Linux AS (Advanced Server) version 2.1 all versionsfixedredhat_csafUScpe:/o:redhat:enterprise_linux:2.1::as
- Red Hat Enterprise Linux ES version 2.1all versionsfixedredhat_csafUScpe:/o:redhat:enterprise_linux:2.1::es
- Red Hat Enterprise Linux WS version 2.1all versionsfixedredhat_csafUScpe:/o:redhat:enterprise_linux:2.1::ws
- Red Hat Linux Advanced Workstation 2.1all versionsfixedredhat_csafUScpe:/o:redhat:enterprise_linux:2.1::aw
- Stronghold 4 for Red Hat Enterprise Linuxall versionsfixedredhat_csafUScpe:/a:redhat:rhel_stronghold:4
advisories (6)
Vendor and ecosystem advisories describing this.
- RHSA-2003:082Red Hat Security Advisory: apache, openssl, php, tomcat security update for Stronghold2003-03-03csaf · redhat_csafUS
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.
- RHSA-2003:083Red Hat Security Advisory: apache security update for Stronghold2003-06-18csaf · redhat_csafUS
Updated Apache packages are available which fix a security issue by preventing control characters from being written to the error log. The updated packages also include a minor bug fix for mod_proxy.
- RHSA-2003:104Red Hat Security Advisory: apache, openssl, php security update for Stronghold2003-03-18csaf · redhat_csafUS
Updated versions of Stronghold 3.0 are available to fix a number of vulnerabilities in OpenSSL, Apache, and PHP.
- RHSA-2003:139Red Hat Security Advisory: : Updated httpd packages fix security vulnerabilities.2003-04-09csaf · redhat_csafUS
Updated httpd packages which fix a number of security issues are now available for Red Hat Linux 8.0 and 9.
- RHSA-2003:243Red Hat Security Advisory: : Updated Apache and mod_ssl packages fix security vulnerabilities2003-09-22csaf · redhat_csafUS
Updated Apache and mod_ssl packages that fix several minor security issues are now available for Red Hat Linux 7.1, 7.2, and 7.3.
- RHSA-2003:244Red Hat Security Advisory: apache security update2003-09-22csaf · redhat_csafUS
Updated Apache and mod_ssl packages that fix several minor security issues are now available for Red Hat Enterprise Linux.
also known as (2)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (76)
External citations — patches, advisories, analysis.
- http://archives.neohapsis.com/archives/vulnwatch/2003-q1/0093.htmlenisa_euvd
- http://frontal2.mandriva.com/security/advisories?name=MDKSA-2004:046enisa_euvd
- http://marc.info/?l=bugtraq&m=104612710031920&w=2enisa_euvd
- http://marc.info/?l=bugtraq&m=108369640424244&w=2enisa_euvd
- http://marc.info/?l=bugtraq&m=108437852004207&w=2enisa_euvd
- http://marc.info/?l=bugtraq&m=108731648532365&w=2enisa_euvd
- http://security.gentoo.org/glsa/glsa-200405-22.xmlenisa_euvd
- http://sunsolve.sun.com/search/document.do?assetkey=1-26-101555-1enisa_euvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan