CVE-2000-1205: XSS

Published Feb 1, 2000
·
Updated

Cross site scripting vulnerabilities in Apache 1.3.0 through 1.3.11 allow remote attackers to execute script as other web site visitors via (1) the printenv CGI (printenv.pl), which does not encode its output, (2) pages generated by the apsenderrorresponse function such as a default 404, which does not add an explicit charset, or (3) various messages that are generated by certain Apache modules or core code. NOTE: the printenv issue might still exist for web browsers that can render text/plain content types as HTML, such as Internet Explorer, but CVE regards this as a design limitation of those browsers, not Apache. The printenv.pl/acuparam vector, discloser on 20070724, is one such variant.

Affected Software

12 affected components
Apache HTTP Server=1.3.0
Apache HTTP Server=1.3.1
Apache HTTP Server=1.3.2
Apache HTTP Server=1.3.3
Apache HTTP Server=1.3.4
Apache HTTP Server=1.3.5
Apache HTTP Server=1.3.6
Apache HTTP Server=1.3.7
Apache HTTP Server=1.3.8
Apache HTTP Server=1.3.9
Apache HTTP Server=1.3.10
Apache HTTP Server=1.3.11

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove printenv.pl (printenv CGI) from your environment.

    Remove or disable the printenv CGI (printenv.pl) from the server (e.g., from cgi-bin) if it is not required; printenv.pl does not encode its output and can enable XSS.

  2. Configuration

    Ensure error responses (for example default 404 pages generated by ap_send_error_response) include an explicit charset in the Content-Type header so they are not misinterpreted by browsers as HTML.

    Apache Http Server (ap_send_error_response) error response charset = explicit charset
  3. Configuration

    Ensure messages generated by Apache modules or core code are HTML-encoded or escaped before being sent to clients to prevent cross-site scripting.

    Apache Http Server (modules/core-generated messages) output encoding / HTML escaping = encode or escape HTML special characters

Event History

Feb 1, 2000
CVE Published
05:00 AM
Data Sourced
via NVD·05:00 AM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 31, 2002
CVE Published
via MITRE·04:00 AM
Data Sourced
via MITRE·04:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2000-1205?

The severity of CVE-2000-1205 is considered high due to its potential for cross-site scripting attacks.

2

How do I fix CVE-2000-1205?

To fix CVE-2000-1205, upgrade Apache HTTP Server to version 1.3.12 or later which includes security patches.

3

What types of Apache HTTP Server versions are affected by CVE-2000-1205?

CVE-2000-1205 affects Apache HTTP Server versions from 1.3.0 through 1.3.11.

4

What vulnerability does CVE-2000-1205 exploit?

CVE-2000-1205 exploits cross-site scripting vulnerabilities in the printenv CGI and custom error pages.

5

Can CVE-2000-1205 affect user data security?

Yes, CVE-2000-1205 can compromise user data security by allowing attackers to execute scripts on behalf of other users.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203