Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

puresecure vulnerabilities and fixes

Recent CVEs affecting puresecure, with upgrade or downgrade steps. 2 tracked.

puresecure has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2003-05-21. Highest priority: CVE-2002-0539 (score 60/100).

FAQ

How do I fix puresecure 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 puresecure being exploited right now?

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

Which puresecure CVE should I patch first?

CVE-2002-0539 currently ranks highest (60/100): Demarc PureSecure 1.05 allows remote attackers to gain administrative privileges via a SQL injection attack in.

← Back to latest CVEs