What is the severity of CVE-2002-2010?

CVE-2002-2010 is classified as a medium severity vulnerability due to its potential for cross-site scripting attacks.

How do I fix CVE-2002-2010?

To fix CVE-2002-2010, upgrade to updated versions of ht://Dig that address the XSS vulnerability.

Which versions are affected by CVE-2002-2010?

CVE-2002-2010 affects ht://Dig versions 3.1.5, 3.1.6, 3.2.0, and 3.2.0b3.

What should I do if I cannot upgrade to fix CVE-2002-2010?

If you cannot upgrade, implement web application firewalls or input validation measures to help mitigate CVE-2002-2010.

Vulnerability/
CVE-2002-2010

medium

4.3

CWE

NVD-CWE-Other 79

31/12/2002

14/7/2005

16/9/2024

CVE-2002-2010: XSS

First published: Tue Dec 31 2002(Updated: )

Cross-site scripting (XSS) vulnerability in htsearch.cgi in htdig (ht://Dig) 3.1.5, 3.1.6, and 3.2 allows remote attackers to inject arbitrary web script or HTML via the words parameter.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
ht://Dig	=3.1.5
ht://Dig	=3.2.0b3
ht://Dig	=3.1.6
ht://Dig	=3.2.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2002-2010?
CVE-2002-2010 is classified as a medium severity vulnerability due to its potential for cross-site scripting attacks.
How do I fix CVE-2002-2010?
To fix CVE-2002-2010, upgrade to updated versions of ht://Dig that address the XSS vulnerability.
Which versions are affected by CVE-2002-2010?
CVE-2002-2010 affects ht://Dig versions 3.1.5, 3.1.6, 3.2.0, and 3.2.0b3.
What is the impact of CVE-2002-2010?
The impact of CVE-2002-2010 allows remote attackers to inject arbitrary web scripts or HTML into the application.
What should I do if I cannot upgrade to fix CVE-2002-2010?
If you cannot upgrade, implement web application firewalls or input validation measures to help mitigate CVE-2002-2010.

agent/type
agent/first-publish-date
agent/softwarecombine
agent/severity
agent/author
agent/weakness
agent/references
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
vendor/htdig
canonical/ht://dig
version/ht://dig/3.1.5
version/ht://dig/3.2.0b3
version/ht://dig/3.1.6
version/ht://dig/3.2.0

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2002-2010?
CVE-2002-2010 is classified as a medium severity vulnerability due to its potential for cross-site scripting attacks.
How do I fix CVE-2002-2010?
To fix CVE-2002-2010, upgrade to updated versions of ht://Dig that address the XSS vulnerability.
Which versions are affected by CVE-2002-2010?
CVE-2002-2010 affects ht://Dig versions 3.1.5, 3.1.6, 3.2.0, and 3.2.0b3.
What is the impact of CVE-2002-2010?
The impact of CVE-2002-2010 allows remote attackers to inject arbitrary web scripts or HTML into the application.
What should I do if I cannot upgrade to fix CVE-2002-2010?
If you cannot upgrade, implement web application firewalls or input validation measures to help mitigate CVE-2002-2010.

CVE-2002-2010: XSS

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2002-2010?

How do I fix CVE-2002-2010?

Which versions are affected by CVE-2002-2010?

What is the impact of CVE-2002-2010?

What should I do if I cannot upgrade to fix CVE-2002-2010?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2002-2010?

How do I fix CVE-2002-2010?

Which versions are affected by CVE-2002-2010?

What is the impact of CVE-2002-2010?

What should I do if I cannot upgrade to fix CVE-2002-2010?