Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

aspedit vulnerabilities and fixes

Recent CVEs affecting aspedit, with upgrade or downgrade steps. 1 tracked.

aspedit has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2005-12-31. Highest priority: CVE-2005-4777 (score 32/100).

FAQ

How do I fix aspedit vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is aspedit being exploited right now?

None of the tracked aspedit CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which aspedit CVE should I patch first?

CVE-2005-4777 currently ranks highest (32/100): Tashcom ASPEdit 2.9 stores the administration password (aka the FTP password) in cleartext in the registry, wh.

← Back to latest CVEs