CVE-2002-1863: Medium severity Iomega Network Attached Storage vulnerability

Published Dec 31, 2002
·
Updated

Iomega Network Attached Storage (NAS) A300U, and possibly other models, does not allow the FTP service to be disabled, which allows local users to access home directories via FTP even when access to all shared directories have been disabled.

Affected Software

1 affected component
Iomega Network Attached Storage=a300u

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Block FTP traffic (TCP ports 20 and 21) to the Iomega NAS devices (e.g., A300U) at the network perimeter and on internal network segments where user workstations reside. Implement firewall or switch ACL rules that deny TCP 20/21 to the NAS IP addresses to prevent FTP access to home directories.

  2. Compensating control

    Restrict access to the NAS management and FTP service to a trusted management network or specific administrative IP addresses only. Implement firewall rules or VLAN segmentation so that only authorized management hosts can reach the NAS administration/FTP ports.

Event History

Dec 31, 2002
CVE Published
05:00 AM
Data Sourced
via NVD·05:00 AM
DescriptionSeverityAffected Software
Jun 28, 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-1863?

CVE-2002-1863 is classified as a moderate severity vulnerability due to its potential for unauthorized access to sensitive data.

2

How do I fix CVE-2002-1863?

To mitigate CVE-2002-1863, ensure that access to FTP services is restricted and implement network segmentation.

3

Who is affected by CVE-2002-1863?

CVE-2002-1863 affects Iomega Network Attached Storage A300U and possibly other models that do not allow FTP service to be disabled.

4

What are the consequences of CVE-2002-1863?

The consequences of CVE-2002-1863 include unauthorized local access to home directories even when shared directory access is disabled.

5

Is CVE-2002-1863 currently being exploited in the wild?

There are no current reports indicating that CVE-2002-1863 is actively being exploited in the wild, but it remains a potential security risk.

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