What is the severity of CVE-1999-1266?

The severity of CVE-1999-1266 is considered medium as it allows attackers to enumerate valid usernames on the system.

How do I fix CVE-1999-1266?

To fix CVE-1999-1266, you should disable or restrict access to the rsh daemon and consider using more secure alternatives like ssh.

What systems are affected by CVE-1999-1266?

CVE-1999-1266 affects systems running the rsh daemon, including versions of Metamail up to 7.2.

What is the impact of CVE-1999-1266?

The impact of CVE-1999-1266 is that it can lead to unauthorized users gaining knowledge of valid usernames, assisting in further attacks.

Is CVE-1999-1266 still a concern today?

While CVE-1999-1266 originated in 1999, systems using outdated software that still employs the rsh daemon remain at risk.

Vulnerability/
CVE-1999-1266

medium

CWE

NVD-CWE-Other

13/6/1997

12/9/2001

20/11/2024

CVE-1999-1266

First published: Fri Jun 13 1997(Updated: )

rsh daemon (rshd) generates different error messages when a valid username is provided versus an invalid name, which allows remote attackers to determine valid users on the system.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
Metamail corporation Metamail	<=7.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-1999-1266?
The severity of CVE-1999-1266 is considered medium as it allows attackers to enumerate valid usernames on the system.
How do I fix CVE-1999-1266?
To fix CVE-1999-1266, you should disable or restrict access to the rsh daemon and consider using more secure alternatives like ssh.
What systems are affected by CVE-1999-1266?
CVE-1999-1266 affects systems running the rsh daemon, including versions of Metamail up to 7.2.
What is the impact of CVE-1999-1266?
The impact of CVE-1999-1266 is that it can lead to unauthorized users gaining knowledge of valid usernames, assisting in further attacks.
Is CVE-1999-1266 still a concern today?
While CVE-1999-1266 originated in 1999, systems using outdated software that still employs the rsh daemon remain at risk.

agent/references
agent/type
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/description
agent/last-modified-date
agent/author
agent/softwarecombine
agent/event
agent/source
agent/tags
collector/nvd-historical
vendor/metamail corporation
product/metamail
canonical/metamail corporation metamail
agent/software-canonical-lookup-request
collector/nvd-api
source/NVD
agent/software-canonical-lookup
collector/nvd-index
version/metamail corporation metamail/7.2

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-1999-1266?
The severity of CVE-1999-1266 is considered medium as it allows attackers to enumerate valid usernames on the system.
How do I fix CVE-1999-1266?
To fix CVE-1999-1266, you should disable or restrict access to the rsh daemon and consider using more secure alternatives like ssh.
What systems are affected by CVE-1999-1266?
CVE-1999-1266 affects systems running the rsh daemon, including versions of Metamail up to 7.2.
What is the impact of CVE-1999-1266?
The impact of CVE-1999-1266 is that it can lead to unauthorized users gaining knowledge of valid usernames, assisting in further attacks.
Is CVE-1999-1266 still a concern today?
While CVE-1999-1266 originated in 1999, systems using outdated software that still employs the rsh daemon remain at risk.