What is the severity of CVE-2002-0480?

CVE-2002-0480 is considered to have a high severity due to the potential for unauthorized access and manipulation of security settings.

How do I fix CVE-2002-0480?

To fix CVE-2002-0480, upgrade ISS RealSecure to the latest version where this vulnerability has been patched.

What systems are affected by CVE-2002-0480?

CVE-2002-0480 affects ISS RealSecure for Nokia devices running versions before IPSO build 6.0.2001.141d.

What are the potential impacts of CVE-2002-0480?

The potential impacts of CVE-2002-0480 include unauthorized key management and possible exploitation by remote attackers.

Is CVE-2002-0480 still a concern today?

While CVE-2002-0480 was reported over two decades ago, it remains a concern for any unpatched systems still in use.

Vulnerability/
CVE-2002-0480

critical

CWE

NVD-CWE-Other

11/6/2002

8/8/2024

CVE-2002-0480

First published: Tue Jun 11 2002(Updated: )

ISS RealSecure for Nokia devices before IPSO build 6.0.2001.141d is configured to allow a user "skank" on a machine "starscream" to become a key manager when the "first time connection" feature is enabled and before any legitimate administrators have connected, which could allow remote attackers to gain access to the device during installation.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
ISS RealSecure	=6.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2002-0480?
CVE-2002-0480 is considered to have a high severity due to the potential for unauthorized access and manipulation of security settings.
How do I fix CVE-2002-0480?
To fix CVE-2002-0480, upgrade ISS RealSecure to the latest version where this vulnerability has been patched.
What systems are affected by CVE-2002-0480?
CVE-2002-0480 affects ISS RealSecure for Nokia devices running versions before IPSO build 6.0.2001.141d.
What are the potential impacts of CVE-2002-0480?
The potential impacts of CVE-2002-0480 include unauthorized key management and possible exploitation by remote attackers.
Is CVE-2002-0480 still a concern today?
While CVE-2002-0480 was reported over two decades ago, it remains a concern for any unpatched systems still in use.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/last-modified-date
agent/author
agent/first-publish-date
agent/event
agent/description
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
vendor/iss
canonical/iss realsecure
version/iss realsecure/6.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-0480?
CVE-2002-0480 is considered to have a high severity due to the potential for unauthorized access and manipulation of security settings.
How do I fix CVE-2002-0480?
To fix CVE-2002-0480, upgrade ISS RealSecure to the latest version where this vulnerability has been patched.
What systems are affected by CVE-2002-0480?
CVE-2002-0480 affects ISS RealSecure for Nokia devices running versions before IPSO build 6.0.2001.141d.
What are the potential impacts of CVE-2002-0480?
The potential impacts of CVE-2002-0480 include unauthorized key management and possible exploitation by remote attackers.
Is CVE-2002-0480 still a concern today?
While CVE-2002-0480 was reported over two decades ago, it remains a concern for any unpatched systems still in use.