Menu

Star on GitHub · 3.2k

CVE-2005-1668

7.5 · HIGH

YusASP Web Asset Manager 1.0 allows remote attackers to gain privileges via a direct request to assetmanager.asp.

Published May 18, 2005yusaspCWE-425EPSS 1.99%

Overview

CVE-2005-1668 is a high-severity vulnerability affecting yusasp web_asset_manager. It was published on May 18, 2005 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

YusASP Web Asset Manager 1.0 allows remote attackers to gain privileges via a direct request to assetmanager.asp.

Remediation

Check the references section for vendor advisories and patches from yusasp. Update web_asset_manager to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2005-1668?

CVE-2005-1668 is a high-severity vulnerability affecting yusasp web_asset_manager. It was published on May 18, 2005 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2005-1668?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2005-1668?

Check the references section for vendor advisories and patches from yusasp. Update web_asset_manager to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2005-1668?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2005-1668 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2005

View all