CVE-2002-2049: High severity Dug Song Dsniff vulnerability

Published Dec 31, 2002
·
Updated

configure for Dsniff 2.3, fragroute 1.2, and fragrouter 1.6, when downloaded from monkey.org on May 17, 2002, has been modified to contain a backdoor, which allows remote attackers to access the system.

Affected Software

3 affected components
Dug Song Dsniff=2.3
Dug Song Fragroute=1.2
Dug Song Fragrouter=1.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Operational

    If you downloaded the 'configure' file for Dsniff version 2.3 from monkey.org on May 17, 2002, assume it was modified to include a backdoor. Treat systems built with that 'configure' as potentially compromised: remove any binaries produced from that build, obtain a verified clean copy from a trusted source, rebuild/reinstall from the clean sources, perform forensic analysis of affected hosts, and rotate any credentials or keys that may have been used on those hosts.

  2. Operational

    If you downloaded the 'configure' file for fragroute version 1.2 from monkey.org on May 17, 2002, assume it was modified to include a backdoor. Treat systems built with that 'configure' as potentially compromised: remove any binaries produced from that build, obtain a verified clean copy from a trusted source, rebuild/reinstall from the clean sources, perform forensic analysis of affected hosts, and rotate any credentials or keys that may have been used on those hosts.

  3. Operational

    If you downloaded the 'configure' file for fragrouter version 1.6 from monkey.org on May 17, 2002, assume it was modified to include a backdoor. Treat systems built with that 'configure' as potentially compromised: remove any binaries produced from that build, obtain a verified clean copy from a trusted source, rebuild/reinstall from the clean sources, perform forensic analysis of affected hosts, and rotate any credentials or keys that may have been used on those hosts.

Event History

Dec 31, 2002
CVE Published
05:00 AM
Data Sourced
via NVD·05:00 AM
RemedyDescriptionSeverityAffected Software
Jul 14, 2005
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-2002-2049?

CVE-2002-2049 is considered to be a high severity vulnerability due to its ability to allow remote attackers to gain unauthorized access to the system.

2

How do I fix CVE-2002-2049?

To fix CVE-2002-2049, immediately remove the affected versions of Dsniff 2.3, Fragroute 1.2, and Fragrouter 1.6 from your system.

3

What software versions are affected by CVE-2002-2049?

CVE-2002-2049 affects Dsniff version 2.3, Fragroute version 1.2, and Fragrouter version 1.6.

4

What type of backdoor is associated with CVE-2002-2049?

CVE-2002-2049 is associated with a backdoor that enables remote attackers to access and control the compromised system.

5

Is CVE-2002-2049 still a threat today?

While CVE-2002-2049 pertains to older software, if the affected versions are still in use, they remain a significant security threat.

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