CVE-2002-0539: Demarc PureSecure 1.05 allows remote attackers to gain administrative privileges via a SQL injection attack in

This week

HIGH 10.0DOWNGRADE

CVE-2002-0539 is a high-severity flaw (CVSS 10.0) affecting puresecure. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Demarc PureSecure 1.05 allows remote attackers to gain administrative privileges via a SQL injection attack in a session ID that is stored in the s_key cookie.

Why this priority

Critical severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	10.0 (High)
EPSS exploit chance	2.1% (top 19%)
CISA exploited list	No
Published	2002-07-03
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: demarc security

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2002-07-03 04:00 UTCPublished CVE record published
2026-06-16 21:57 UTCUpdated Record last modified

demarc security puresecure DOWNGRADE

Affected: 1.0.5_for_unix · 1.0.5_for_windows

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.5_for_unix

1. Check installed version

apt-cache policy puresecure || rpm -q puresecure || puresecure --version

2. No fixed release: DOWNGRADE to a release before 1.0.5_for_unix (Debian / Ubuntu)

apt-cache madison puresecure sudo apt install puresecure=<VERSION_BEFORE_1.0.5_for_unix> sudo apt-mark hold puresecure

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list puresecure sudo dnf downgrade puresecure-<VERSION_BEFORE_1.0.5_for_unix> sudo dnf versionlock add puresecure

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Demarc PureSecure 1.0.5 - Authentication Check SQL Injection

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2002-0539?

puresecure: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2002-0539 being exploited?

CVE-2002-0539 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2002-0539 affect?

CVE-2002-0539 affects puresecure. Severity is high (CVSS 10.0). Demarc PureSecure 1.05 allows remote attackers to gain administrative privileges via a SQL injection attack in a session ID that is stored in the s_key cookie.

How urgent is CVE-2002-0539?

Priority 60/100. Critical severity; Public exploit reference

Related CVEs

CVE-2003-0340 HIGH 7.5 DOWNGRADE Demarc Puresecure 1.6 stores authentication information for the logging server in plaintext, which allows atta

References

← Back to latest CVEs